Right. My next project is building a webserver, and there are a few things I need advice about. Bear in mind that there isn't any goal to it other than the actual webserver itself - I don't have any particular website I want to get running, so please don't suggest commercial hosting: I just want to build my own (secure) webserver. Other than that feel free to destroy my ideas, but preferably only if you have better ones
The hardware itself (an old PII) has been put together, so mainly I'm looking for software advice. Currently I'd go for Apache running on FreeBSD.
1. Is there a better way to do it? I'll freely admit I don't have any experience of UNIX, but I'm willing to learn. If I do go this route, should I go for Apache-SSL rather than straight Apache?
2. My NIC (and probably more) isn't explicitly mentioned in the FreeBSD hardware support notes; I realise that only means it hasn't been proven to work, but how hardware-friendly is it going to be?
Now, obviously the computer needs to be accessible from the internet. Physically it will be located next to my main computer which has a wireless connection to the ADSL router downstairs, so:
3. If I used crossover cable to connect the webserver and my main rig, would I be able to put the webserver on the same network as the router & the other two computers in the house? Or would I have to buy another wireless adaptor to achieve this?
4. I think the answer to Q3 is that it can go on the same network, so if that's right, would I then be better off putting the existing wireless dongle on the webserver or my main rig? I'm guessing it'd be better on the main rig for security (as that computer would ignore any traffic being sent through it for the webserver?), but that'd mean leaving it on all the time.
5. (Bit more general this one) How much control is possible over a network? I guess this will probably depend on the OS, but I don't really want to buy a KVM switch if I don't have to
Thanks in advance!