3 ms·

don't completely agree. OP wants to get to grips with server administration, not with linux. ubuntu, or any other easy distro/debian derivative will do just fin

by jcfrei 14y ago

don't completely agree. OP wants to get to grips with server administration, not with linux. ubuntu, or any other easy distro/debian derivative will do just fine. I would further recommend the installation of nginx, which is fairly easy, just make sure you take the slightly more difficult path by compiling it yourself (will give you a little insight into makefiles). configuring your nginx.conf and default sites will provide further insight into server administration. the documentation for nginx is top notch, plus you got a fast server running, which will fit most of your use cases.

loxs 14y ago
I disagree. I will ask you several questions. You probably know their answers. And the OP probably doesn't (at least not all). * What is a network interface? * What is localhost? * What is a reverse proxy? Why the hell does one need that? Apache didn't require to become one in order to run my PHP programs? * What is a Makefile? What is a compiler? * What is a SSH tunnel? Now tell me, do you think it's a good idea for someone who doesn't understand these topics like the palm of their hand, to run their own server?
- jcfrei 14y ago
  yes, I do think it's a good idea. we're talking about a novice here, who won't run a site that requires 99.9999% uptime and with your selection of topics you're probably already digging too deep into marginally relevant technicals. they are in my opinion not required for successfully running a server (except maybe for the reverse proxy), however I believe you failed to mention a few things I would find very important: focus much more on the security side when you're running your own webstack. things like: * restricting .htaccess and other folders * escaping mysql requests from user input * sanitizing user input * handle DDoS attacks, spam prevention * correctly setting exipration dates for caching * DNS configuration (round robin, etc.) * correct amount of worker process Calomel.org has got an excellent guide for setting up your nginx server https://calomel.org/nginx.html https://calomel.org/nginx.html

by jcfrei 14y ago

loxs 14y ago

I disagree. I will ask you several questions. You probably know their answers. And the OP probably doesn't (at least not all). * What is a network interface? * What is localhost? * What is a reverse proxy? Why the hell does one need that? Apache didn't require to become one in order to run my PHP programs? * What is a Makefile? What is a compiler? * What is a SSH tunnel? Now tell me, do you think it's a good idea for someone who doesn't understand these topics like the palm of their hand, to run their own server?

jcfrei 14y ago
yes, I do think it's a good idea. we're talking about a novice here, who won't run a site that requires 99.9999% uptime and with your selection of topics you're probably already digging too deep into marginally relevant technicals. they are in my opinion not required for successfully running a server (except maybe for the reverse proxy), however I believe you failed to mention a few things I would find very important: focus much more on the security side when you're running your own webstack. things like: * restricting .htaccess and other folders * escaping mysql requests from user input * sanitizing user input * handle DDoS attacks, spam prevention * correctly setting exipration dates for caching * DNS configuration (round robin, etc.) * correct amount of worker process Calomel.org has got an excellent guide for setting up your nginx server https://calomel.org/nginx.html https://calomel.org/nginx.html