Skip to content

Commit dd663d6

Browse files
authoredNov 7, 2024··
Add example command for copying (#2327)
As for #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>
1 parent b9ed242 commit dd663d6

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed
 

‎README.md

+4
Original file line numberDiff line numberDiff line change
@@ -242,6 +242,10 @@ During a fresh Nextcloud installation, the latest version (from the image) of th
242242
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.
243243

244244
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`.
245+
A command to copy these configs would e.g. be:
246+
```console
247+
docker exec <container-name> sh -c "cp /usr/src/nextcloud/config/*.php /var/www/html/config"
248+
```
245249

246250
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).
247251

0 commit comments

Comments
 (0)
Please sign in to comment.