friendica/friendica
6
0
Fork 1
mirror of https://github.com/friendica/friendica synced 2024-05-13 19:09:40 +02:00
Code Issues Packages Projects Releases 1 Wiki Activity

Updated Running a public or community server (markdown)

MartinFarrent 2012-05-24 14:59:17 -07:00
parent bd25f7eb17
commit d4174c8994
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
Running-a-public-or-community-server.md

@ -12,15 +12,15 @@ The distinction is important. For instance, registration policy is affected. If
Both types of site have lots in common, but there are some important differences too. A community server knows how many users it will have and can purchase resources accordingly. A public server will either have to upgrade frequently, or keep an eye on it's resources carefully to know when to stop accepting sign ups.
***The technical environment***
***The technical environment - operating system***
Choosing the right initial environment is a fundamental part of managing a public or community server. Obviously, you won't normally try to host large numbers of users on a shared hosting scheme - you will almost always choose a Virtual Private Server (VPS) with an upgradable plan (or even a dedicated server if you expect extremely heavy use). But there are other considerations, too.
One pertains to the operating system. Our advice is to use Debian unless you are intimate with another Linux OS. The reason for this is simple: Debian is the most popular operating system among the people who usually offer support in the public Friendica groups. When you have problems later - and even the most experienced among us run into riddles from time to time - you'll find it much harder to get support and spend more time on search engines if you're using a different distro. This isn't (just) evangelism, we've already had users on CentOS and Fedora who had to wait _hours_ to find support because nobody else is familiar with the particular quirks of their systems. If you really know your way around, and you know where all your configuration and log files are without help, feel free to use something else, but unless you're intimate with your OS of choice, stick with Debian.
One pertains to the operating system. Our advice is to use Debian unless you are intimate with another Linux OS. The reason for this is simple: Debian is easily the most popular operating system among the people who usually offer support in the public Friendica groups. When you have problems later - and even the most experienced among us run into riddles from time to time - you'll find it much harder to get help and will spend more time on search engines if you're using a different distro. This isn't evangelism: We've already had users on CentOS and Fedora who had to wait _hours_ to find support because nobody else is familiar with the particular quirks of their systems. If you really know your way around, and you know where all your configuration and log files are without help, feel free to any Linux flavour you like - but unless you're intimate with your OS of choice, stick with Debian (and not a derivative like Ubuntu - there are significant differences).
Ubuntu isn't Debian.
***Web server***
2. Use Nginx. Nginx offers superior performance to Apache and can handle around twice as many users on average - sometimes more. 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 automagically in ten minutes flat. Literally. You can, of course, use Apache without any problems if your server is already set up and installed, you just 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 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.
3. Drop the WWW. Some people still go to the effort of inserting www into web addresses, for some reason. This breaks things. Use an nginx rule or Apache redirect to send http://www.domain.com traffic to plain old http://domain.com