diff options
| author | rugk <rugk+git@posteo.de> | 2024-11-08 00:38:16 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-11-07 23:38:16 +0000 |
| commit | dd663d60c69954c0b50b68c4d870f9910ddbfab9 (patch) | |
| tree | 15ff5e0a619db2347e1ff2ce6f28220ef05a4982 | |
| parent | b9ed2426a0a2c7feb954c9b722d1390cc8fbd26b (diff) | |
As for https://github.com/nextcloud/docker/issues/2266 and the re-appearing message IMHO, it is quite convenient to have a command to copy here if you just have not changed any config files…
Signed-off-by: rugk <rugk+git@posteo.de>
| -rw-r--r-- | README.md | 4 |
1 files changed, 4 insertions, 0 deletions
@@ -242,6 +242,10 @@ During a fresh Nextcloud installation, the latest version (from the image) of th The copied files, however, are **not** automatically overwritten whenever you update your environment with a newer Nextcloud image. This is to prevent local changes in `/var/www/html/config` from being unexpectedly overwritten. This may lead to your image-specific configuration files becoming outdated and image functionality not matching that which is documented. A warning will be generated in the container log output when outdated image-specific configuration files are detected at startup in a running container. When you see this warning, you should manually compare (or copy) the files from `/usr/src/nextcloud/config` to `/var/www/html/config`. +A command to copy these configs would e.g. be: +```console +docker exec <container-name> sh -c "cp /usr/src/nextcloud/config/*.php /var/www/html/config" +``` As long as you have not modified any of the provided config files in `/var/www/html/config` (other than `config.php`) or only added new ones with names that do not conflict with the image specific ones, copying the new ones into place should be safe (but check the source path `/usr/src/nextcloud/config` for any newly named config files to avoid new overlaps just in case). |