public/nixpkgs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

nixos/nextcloud: apply doc fixes suggested by fabaff

Browse Source 
Co-authored-by: Fabian Affolter <mail@fabian-affolter.ch>
(cherry picked from commit 767bb4e4bbb9a8d06d4c3cbc14092902c2465f98)
This commit is contained in:
Maximilian Bosch
2021-08-31 18:54:20 +00:00
committed by github-actions[bot]
parent c19b0bf9de
commit ebd597d2f3
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
nixos/modules/services/web-apps/nextcloud.xml
+5 -5
View File
@@ -96,14 +96,14 @@
managing its own configuration. The config file lives in the home directory managing its own configuration. The config file lives in the home directory
of the <literal>nextcloud</literal> user (by default of the <literal>nextcloud</literal> user (by default
<literal>/var/lib/nextcloud/config/config.php</literal>) and is also used to <literal>/var/lib/nextcloud/config/config.php</literal>) and is also used to
track several states of the application (e.g. whether installed or not). track several states of the application (e.g., whether installed or not).
</para> </para>
</formalpara> </formalpara>
<para> <para>
All configuration parameters are also stored in All configuration parameters are also stored in
<filename>/var/lib/nextcloud/config/override.config.php</filename> which is generated by <filename>/var/lib/nextcloud/config/override.config.php</filename> which is generated by
the module and linked from the store to ensure that all values from the module and linked from the store to ensure that all values from
<filename>config.php</filename>can be modified by the module. <filename>config.php</filename> can be modified by the module.
However <filename>config.php</filename> manages the application's state and shouldn't be However <filename>config.php</filename> manages the application's state and shouldn't be
touched manually because of that. touched manually because of that.
</para> </para>
@@ -123,7 +123,7 @@
<formalpara> <formalpara>
<title>Multiple version upgrades</title> <title>Multiple version upgrades</title>
<para> <para>
Nextcloud doesn't allow to move more than one major-version forward. If you're e.g. on Nextcloud doesn't allow to move more than one major-version forward. E.g., if you're on
<literal>v16</literal>, you cannot upgrade to <literal>v18</literal>, you need to upgrade to <literal>v16</literal>, you cannot upgrade to <literal>v18</literal>, you need to upgrade to
<literal>v17</literal> first. This is ensured automatically as long as the <literal>v17</literal> first. This is ensured automatically as long as the
<link linkend="opt-system.stateVersion">stateVersion</link> is declared properly. In that case <link linkend="opt-system.stateVersion">stateVersion</link> is declared properly. In that case
@@ -152,7 +152,7 @@
<listitem> <listitem>
<para> <para>
If this occurs on an <emphasis>existing</emphasis> setup, this is most likely because If this occurs on an <emphasis>existing</emphasis> setup, this is most likely because
the maintenance-mode is active. It can be deactivated by running the maintenance mode is active. It can be deactivated by running
<command>nextcloud-occ maintenance:mode --off</command>. It's advisable though to <command>nextcloud-occ maintenance:mode --off</command>. It's advisable though to
check the logs first on why the maintenance mode was activated. check the logs first on why the maintenance mode was activated.
</para> </para>
@@ -163,7 +163,7 @@
<para> <para>
A re-run of the installer can be forced by <emphasis>deleting</emphasis> A re-run of the installer can be forced by <emphasis>deleting</emphasis>
<filename>/var/lib/nextcloud/config/config.php</filename>. This is the only time <filename>/var/lib/nextcloud/config/config.php</filename>. This is the only time
where this is advisable because the fresh install doesn't have any state that can be lost. advisable because the fresh install doesn't have any state that can be lost.
In case that doesn't help, an entire re-creation can be forced via In case that doesn't help, an entire re-creation can be forced via
<command>rm -rf ~nextcloud/</command>. <command>rm -rf ~nextcloud/</command>.
</para> </para>