mirrors/nextcloud-documentation
3
0
Fork 0
mirror of https://github.com/nextcloud/documentation.git synced 2025-10-26 11:18:02 +00:00
Code Issues Packages Projects Releases Wiki Activity

generate documentation from config.sample.php

Browse Source
This commit is contained in:
Morris Jobke 2017-12-13 03:35:36 +01:00
parent d803a2faaa
commit 94963faa2a
1 changed files with 11 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
admin_manual/configuration_server/config_sample_php_parameters.rst
View File

@ -224,7 +224,11 @@ This sets the default language on your Nextcloud server, using ISO_639-1
language codes such as ``en`` for English, ``de`` for German, and ``fr`` for
French. It overrides automatic language detection on public pages like login
or shared items. User's language preferences configured under "personal ->
language" override this setting after they have logged in.
language" override this setting after they have logged in. Nextcloud has two
distinguished language codes for German, 'de' and 'de_DE'. 'de' is used for
informal German and 'de_DE' for formal German. By setting this value to 'de_DE'
you can enforce the formal version of German unless the user has chosen
something different explicitly.
Defaults to ``en``
@ -321,6 +325,10 @@ The directory where the skeleton files are located. These files will be
copied to the data directory of new users. Leave empty to not copy any
skeleton files.
``{lang}`` can be used as a placeholder for the language of the user.
If the directory does not exist, it falls back to non dialect (from ``de_DE``
to ``de``). If that does not exist either, it falls back to ``default``
Defaults to ``core/skeleton`` in the Nextcloud directory.
::
@ -1266,8 +1274,8 @@ Available failover modes:
WARNING: FAILOVER_DISTRIBUTE is a not recommended setting and we strongly
suggest to not use it if you use Redis for file locking. Due to the way Redis
is synchronised it could happen, that the read for an existing lock is
scheduled to a slave that is not fully synchronised with the connected master
is synchronized it could happen, that the read for an existing lock is
scheduled to a slave that is not fully synchronized with the connected master
which then causes a FileLocked exception.
See https://redis.io/topics/cluster-spec for details about the Redis cluster