Updated Running a public or community server (markdown)

MartinFarrent 2012-05-24 15:24:56 -07:00
parent a9d409b45d
commit 1b77fbabd9

@ -20,7 +20,7 @@ One pertains to the operating system. Our advice is to use Debian unless you are
***Web server***
If you are comfortable with the idea, use Nginx - it offers superior performance to Apache and can handle around twice as many users on average. For bonus points, using Debian and Nginx lets you use the [Debian install script](https://github.com/Keith2/lowendscript-ng) to setup your server almost automatically in ten minutes flat (literally). You can, of course, use Apache without any problems if your server is already set up and installed, but you won't be able to host as many people on your site as an Nginx server.
If you are comfortable with the idea, use Nginx - it offers superior performance to Apache and can handle around twice as many users on average. For bonus points, using Debian and Nginx lets you use the [Debian install script](https://github.com/Keith2/lowendscript-ng) to set up your server almost automatically in ten minutes flat (literally!). You can, of course, use Apache without any problems if your server is already set up and installed, but you won't be able to host as many people on your site as an Nginx server.
On a public or community server, you'll need to block the use of the prefix 'www'. Some people still go to the effort of inserting www into web addresses. This breaks things. Use an Nginx rule or Apache redirect to send http://www.domain.com traffic to plain http://domain.com