The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
Converting an Old PC into a Web Server
NogsCrap, crap, mega crap.Crap, crap, mega crap.Registered Userregular
Should I reformat and go with Linux and try out the LAMP packages? Or should I keep the Windows XP there and go with something like WampServer 2? I definitely want to go with the AMP part though.
Basically, I have an old PC now, and I want to turn it into a web server, so I can 1. Learn how servers work from the inside out and 2. Use it as a testing server while I learn PHP and MySQL.
so you'd say LAMP is probably the way to go over WAMP?
Also, this probably means reformatting to get Ubuntu running, right?
WAMP is possible, but you will find the documentation and support for the AMP of the WAMP almost always assumes a LAMP.
Do I win some sort of prize for that sentence?
Seriously though, a copy of Ubuntu Desktop (or Server) will do everything so smoothly, simply "apt-get install apache" and what have you, and it's all a piece of cake. I setup Ubuntu Server in less than an hour of actual work, including a jail for SSH hax0r attempts (fail2ban). It's just so much easier to get the packages, find the documentation, know where all the log files are...
Lewisham on
0
NogsCrap, crap, mega crap.Crap, crap, mega crap.Registered Userregular
edited December 2009
Cool, ya my only real concern is that this will be my first *real* exposure to a Linux OS. I mean I've used protocols with certain FTP clients for Linux environments. But never actually had L/Unix on a desktop machine to play around with before.
Suppose I should learn it anyways, another skill to add to the resume and all that.
The default installations of most windows home OS' only allow something on the order of 10 connections at once. Unless you want to pony up for a professional or server edition, your best best would be the open source stuff.
Unless you are literally running an actual outward facing website there is no valid reason to favor LAMP over WAMP. This isn't 19-fucking-98, Windows just doesn't roll over and die overnight from some memory access violation.
If you have a windows machine and are comfortable with Windows, just do what makes sense.
Also Tejs you are talking about IIS, that is totally not what is being talked about! Apache runs independently of all that.
Unless you are literally running an actual outward facing website there is no valid reason to favor LAMP over WAMP. This isn't 19-fucking-98, Windows just doesn't roll over and die overnight from some memory access violation.
If you have a windows machine and are comfortable with Windows, just do what makes sense.
Also Tejs you are talking about IIS, that is totally not what is being talked about! Apache runs independently of all that.
well the plan is to have a website hosted on this PC. but basically a purely testing website while i learn the ins-and-outs of Apache, MySQL and PHP.
I suppose I could try and pony up money and just get hosting through InMotion Hosting or something, but I feel like doing it from the ground up will give me a better understanding of how everything works.
When I say outward facing, I mean you would literally be hosting a website and have DNS pointed at your house. Which, of course, you would be insane to do that unless you had a static IP, which you don't.
For internal testing there is nothing in WAMP that should alarm you for any reason as to stability or behavior at all.
Having used WAMP personally, I can say that it is fairly automatic, and Windows features a plethora of easy to use MySQL admin tools to boot which you will want.
Don't let operating system roulette interfere with getting work done.
If you just want to fool around with apache/mysql/php then I suggest you save your old computer and use XAMPP. It's very common to use it on a development machine to just dick around with web programming. If you want to do anything outside of php programming then I suggest you instal WAMP on your current machine.
Eitherway, if you just want a development environment there's no real reason for a solo user to waste a computer for a web server. Why not try building a HTPC out of the old computer instead?
When I say outward facing, I mean you would literally be hosting a website and have DNS pointed at your house. Which, of course, you would be insane to do that unless you had a static IP, which you don't.
Most ISPs also forbid you from doing so in your contract (although enforcement of that is generally on a "when and if you cause problems" basis; ISPs have a huge amount of infrastructure momentum so if the system technically permits you to do something they tend to not change that until you become a problem to be dealt with).
Not that Windows is terribad for hosting, but since knowing linux hosting stuff is very handy for working with actual deployed hosts (many of which are linux) it's a good learning experience to go with LAMP.
Posts
should just give you a single disk installer with everything ready to go.
Also, this probably means reformatting to get Ubuntu running, right?
PARKER, YOU'RE FIRED! <-- My comic book podcast! Satan look here!
WAMP is possible, but you will find the documentation and support for the AMP of the WAMP almost always assumes a LAMP.
Do I win some sort of prize for that sentence?
Seriously though, a copy of Ubuntu Desktop (or Server) will do everything so smoothly, simply "apt-get install apache" and what have you, and it's all a piece of cake. I setup Ubuntu Server in less than an hour of actual work, including a jail for SSH hax0r attempts (fail2ban). It's just so much easier to get the packages, find the documentation, know where all the log files are...
Suppose I should learn it anyways, another skill to add to the resume and all that.
PARKER, YOU'RE FIRED! <-- My comic book podcast! Satan look here!
PARKER, YOU'RE FIRED! <-- My comic book podcast! Satan look here!
If you have a windows machine and are comfortable with Windows, just do what makes sense.
Also Tejs you are talking about IIS, that is totally not what is being talked about! Apache runs independently of all that.
we also talk about other random shit and clown upon each other
well the plan is to have a website hosted on this PC. but basically a purely testing website while i learn the ins-and-outs of Apache, MySQL and PHP.
I suppose I could try and pony up money and just get hosting through InMotion Hosting or something, but I feel like doing it from the ground up will give me a better understanding of how everything works.
PARKER, YOU'RE FIRED! <-- My comic book podcast! Satan look here!
For internal testing there is nothing in WAMP that should alarm you for any reason as to stability or behavior at all.
Having used WAMP personally, I can say that it is fairly automatic, and Windows features a plethora of easy to use MySQL admin tools to boot which you will want.
Don't let operating system roulette interfere with getting work done.
we also talk about other random shit and clown upon each other
And getting familiar with a linux server box is never a bad idea if you're planning on maybe taking this project larger in the future.
Eitherway, if you just want a development environment there's no real reason for a solo user to waste a computer for a web server. Why not try building a HTPC out of the old computer instead?
Most ISPs also forbid you from doing so in your contract (although enforcement of that is generally on a "when and if you cause problems" basis; ISPs have a huge amount of infrastructure momentum so if the system technically permits you to do something they tend to not change that until you become a problem to be dealt with).