Updated Running a public or community server (markdown)

MartinFarrent 2012-05-24 23:54:33 -07:00
parent 8df96e4a12
commit cb885974d3

@ -40,17 +40,17 @@ Don't use command line tools where they can be avoided. Yes, they're quicker, a
Don't use unorthodox solutions suggested by random geeks. Some of them know what they're doing - but know far more than you do and are able to repair their errors quickly, too. Others are just guessing. Stick to the official documentation or to advice issued by the main developers.
***Configuration***
***Initial configuration***
Now you've chosen the right environment and got Friendica installed, you need to do some configuration. You need to put more effort into this than somebody on a private server for the simple reason, other people are using your site.
After choosing the right environment and installing Friendica, you need to do some configuration. You need to put more effort into this than somebody on a private server for the simple reason that other people are using your site. The options described in this section are available in your admin menu's ``Site`` panel and are very easy to configure with the following information on their purposes.
1. Site Name. In most instances, you can call your site Colin if you like, and it won't make a bit of difference. There are two places it is important though - your front page will, by default, pronounce "Welcome To $SiteName" where $SiteName is the value you put in this field. If you are a public server, this will also be your site name as listed in the public server directory. If you change the front page, and choose not to be listed as a public server, go ahead and call it Colin, but if you don't change your front page, or do get listed as a public server, put something suitable here.
1. _Site Name_: Your front page will, by default, pronounce "Welcome To $SiteName" - where $SiteName is the value you put in this field. If you are a public server, this will also be your site name as listed in the public server directory. If you change the front page, and choose not to be listed as a public server.
2. Banner/Logo. This is actually a HTML box where you can put anything at all. You would normally want a logo and your site name in this box, but you can include any arbitrary HTML you want. Bear in mind that each theme will apply it's own style sheet to this entry and it can appear very different in each. The Dispy themes have very large, left aligned text here, for example, and Diabook very small centre aligned text. Make sure your logo links to your home address. If you allow both SSL and non-SSL traffic (which you shouldn't), use "/" for the home link to avoid switching scheme.
2. _Banner/Logo_: This is actually a HTML box where you can put anything at all. You would normally want a logo and your site name in this box, but you can include any arbitrary HTML you want. Bear in mind that each theme will apply it's own style sheet to this entry and it can appear very different in each. For instance, the Dispy themes have very large, left-aligned text here. By contrast Diabook has very small centre-aligned text. Instead of linking to friendica.com (default), you can link your logo to your home address. If you allow both SSL and non-SSL traffic, use "/" for the home link to avoid switching scheme.
3. System Language. On a public server, the system language should normally be set to English, even if you're not English. Friendica will attempt to autodetect the language specified by your visitors browsers. If you have a translation installed for that language, the site will select the correct one automatically. Only if this fails, will the language fall back to the default specified here. English is the de-facto language of the internet and the usual choice here. If you are targeting people from a particular country, go ahead and set their language as the default. If you're a community server, you should set this to the language your particular community speaks.
3. _System Language_: On a public server, the system language should _normally_ be set to English, even if you're not English. Friendica will attempt to auto-detect the language specified by your visitors' browsers. If you have a translation installed for that language, the site will select the correct one automatically. Only if this fails, will the language fall back to the default specified here. English is the de-facto language of the internet and the usual choice here. But if you are targeting people from a particular country, go ahead and set their language as the default. If you're a community server, you should set this to the language your particular community speaks.
4. System Theme. This specifies the default theme for vistors to the website, and members who are not logged in (note you must first activate themes from the "theme" menu). Diabook is the most "newbie friendly" theme, but it has a draw back - it doesn't yet work in internet explorer. The Duepunto themes are the most basic, and should work in most browsers, but they're also the least "shiney". The Comix font is missing from some systems, though the theme still looks nice without it. Other than these considerations, your system theme is a matter of taste. Remember, for some reason, users never seem to find the theme options. You should use the theme you think most people will find easiest to use, not necessarily the one you personally use. For example, I personally use dispy-dark, but I find my users need less help if my system theme is Diabook.
4. _System Theme_: This specifies the default theme for vistors to the website, and members who are not logged in (note you must first activate themes from the "theme" menu). Diabook is the most "newbie friendly" theme, but it has a draw back - it doesn't yet work in internet explorer. The Duepunto themes are the most basic, and should work in most browsers, but they're also the least "shiney". The Comix font is missing from some systems, though the theme still looks nice without it. Other than these considerations, your system theme is a matter of taste. Remember, for some reason, users never seem to find the theme options. You should use the theme you think most people will find easiest to use, not necessarily the one you personally use. For example, I personally use dispy-dark, but I find my users need less help if my system theme is Diabook.
5. SSL policy. If you allow SSL and Non-SSL connections, which you shouldn't for the reasons explained in the earlier section, you should set this to no SSL policy. If you do this, you need to provide a way for users to switch between the two. I use two small padlock icons - one open, one closed - in the Banner/Logo area to achieve this. If you don't have SSL at all, you should also use this option. If you mandate SSL, select the Force all links to use SSL option.