Updated Running a public or community server (markdown)

MartinFarrent 2012-05-25 03:08:17 -07:00
parent 30ad33dd66
commit 1de1ae2978

@ -672,16 +672,16 @@ This is a _directory, not a file_, and must be writeable by the webserver. If y
**Other .htconfig.php settings**
Most of these settings in this section of .htconfig.php are self-explanatory, and have equivalents in the admin panel. It is very important that you don't change settings here _and_ in the admin panel, as this can have unpredictable results. For each setting, use one or the other.
Most of these settings in this final section of our how-to are self-explanatory, and have equivalents in the admin panel. It is very important that you don't change settings here _and_ in the admin panel, as this can have unpredictable results. For each setting, use one or the other.
The only really important setting here is for your maximum daily registrations. You can add a line that looks like this to restrict the number of users who can join in one day:
The only really important setting not mentioned yet is for your maximum daily registrations. You can add a line that looks like this to restrict the number of users who can join in one day:
> $a->config['system']['max_daily_registrations'] = 123;
where 123 is the number of users you'll allow per day. This probably doesn't matter for community servers, or servers that require approval, but it's essential for open public servers. One admin once had one user sign up and then invite twenty friends. They all activated Facebook, and had over 500 friends each. Result: a crippled server for everyone else. Had `max_daily_registrations` been set to 5 or 10, that would never have happened. Use this setting or you _will_ be hit like this eventually.
If you look through your .htconfig.php file, you'll find another example setting with empty fields:
If you look through your .htconfig.php file, you may find another example setting with empty fields:
>// If enabled, all items are cached in the given directory
>$a->config['stem']['itemyscache'] = "";