Skip to content

Update section on config_is_read_only to reflect its changed meaning #7795

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mejo- wants to merge 1 commit into from
Closed

Update section on config_is_read_only to reflect its changed meaning #7795

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions admin_manual/configuration_server/config_sample_php_parameters.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -950,11 +950,11 @@ Defaults to ``true``

In certain environments it is desired to have a read-only configuration file.

When this switch is set to ``true`` Nextcloud will not verify whether the
configuration is writable. However, it will not be possible to configure
all options via the Web interface. Furthermore, when updating Nextcloud
it is required to make the configuration file writable again for the update
process.
When this switch is set to ``true``, writing to the configuration file will
be prevented. Therefore, it will not be possible to configure all options via
the Web interface. Furthermore, when updating Nextcloud it is required to make
the configuration file writable again for the update process and to set this
switch to ``false``.

Defaults to ``false``

Expand Down