I will be building a box specifically for web hosting, but only intended for learning and experimentation. This will not be a production server.

I have decided to stick with the norm for now and use Redhat, Apache, WHM and CPanel.

What is the best way to approach this?
What type of install should I choose?
How would you partition the drive(s)?
What security considerations should I take in to account?
How would you optimize it?
Would you install Gnome, KDE or simply use the command line?

Thanks in advance.

Originally posted by justageek
I will be building a box specifically for web hosting, but only intended for learning and experimentation. This will not be a production server.

Where/how will you run this? What type of services/software are you intending to run?


I have decided to stick with the norm for now and use Redhat, Apache, WHM and CPanel.


Renting a license for cpanel for a test server can be an expensive addition. You might consider not using a control panel at all, if you're learning. It will allow you to get more familiar with how things work without having a GUI do most of the tasks for you.


What is the best way to approach this?


I'd just suggest you install and configure and get familiar with all the issues involved with any and all of the software and tools you intend or want to run on a server, get used to it, educate yourself on it all and take the time to do it right.


What type of install should I choose?


If you want to go with the most common install, you'd probably use Linux Redhat 7.2 or 7.3, use the Apache web server, install all the common things like compilers, Perl, Email software, ProFTP, etc. If you want to use Cpanel, just simply get Redhat 7.2 or 7.3 and install it and it'll install all the rest for you.


How would you partition the drive(s)?


That depends on the size of the drive, how many you have, etc. I'd say you should have a good idea of how large the partitions should be in relation to the size of the drive, what you'll be running and so on. A separate partition for the following is desirable, more stable and secure:
/, /boot, /usr, /var, /tmp, and /home. If you plan to do any real jailing of services, you should have unused space or an extra partition handy, called whatever you wish.


What security considerations should I take in to account?


There's too many to list.


How would you optimize it?


That's too open for an answer. It depends on what you are running and many things are individually optimized (and in different ways).


Would you install Gnome, KDE or simply use the command line?


You definitely do not want a GUI on a web server. Never install any such thing on a web server. It takes up room, has tools nd programs that are not meant to run in a web server environment and therefore open up a lot more security risks.

Originally posted by 2host.com

You definitely do not want a GUI on a web server. Never install any such thing on a web server. It takes up room, has tools nd programs that are not meant to run in a web server environment and therefore open up a lot more security risks.

Sometimes it's handy to have X on your Unix server, as long as you do not allow normal users to access that. For instance, you can connect remotely to your server and use GNORPM instead of the normal command line rpm, browse for files to download using Mozilla, or chat using Yahoo! IM, etc.

I normally use TightVNC (www.tightvnc.com) on LAN. For Internet use it is recommended that you combine TightVNC with stunnel for stronger encryption.

Originally posted by stbauer


Sometimes it's handy to have X on your Unix server, as long as you do not allow normal users to access that. For instance, you can connect remotely to your server and use GNORPM instead of the normal command line rpm, browse for files to download using Mozilla, or chat using Yahoo! IM, etc.

I normally use TightVNC (www.tightvnc.com) on LAN. For Internet use it is recommended that you combine TightVNC with stunnel for stronger encryption.

Running X, etc. on a web server is just not a good idea, at all. I would never suggest it, ever. Yes, you can, it's just not a good idea though. Not to mention that it rarely serves much of a purpose or will really make any task any better. I just don't see the point and there's too many risks and hassles. It's a web server and shouldn't have it. A desktop system, a network/workstation, etc. fine, but a web server, never. Nothing you can run in that regard would be of any advantage for a web server, unless you are doing other stuff with it (like using AIM, a browser, etc.) which is not suggested.

GUIs eat ram... especially if you have it load KDE or GNOME. If you are intent on running a GUI, make sure it is not on the system console (if you want it, run it manually) and setup VNC. Also, use a small window manager like blackbox or something.

I never run X on any of my servers. Then again, I prefer the command line to graphical tools anyway.

I totally agree with you on that. Of all the things i have seen the GUI is the worst thing that happened to Linux. Its Slower/ worse/ buggier then Windows 3.1 in my honest opinion and from my year+ of experience.

If you were smart you might use XServer on it and setup a way to start it and stop it that way you could use some of those programs that setup virtual desktops. But I wouldnt recommend doing it as KDE on a P3 700mhz 256MB has turned out to be slower than AMD K6 233mzh windows 98 32 mb ram.

I notifced those partitions were listed. Any Optimial Sizes for each one. (I saw somebody mention 2 gb for root if you use CPanel)

/
/boot
/usr
/var
/tmp
/home.

I also noted what that one Person mentioned above. He had not found any real good guides For Linux and setting it up in a Web Server Environment save for setting it up as a Personal Warez Server (which is all I have ever seen anybody do).

Does Anybody know of a book or Tutorial that Goes through and describes the process of setting up a Web Server