To the author: thanks for all the work that goes in to sharing this. When people share with this much detail I always find at least a couple things that improve my setups.
Here are some I can share back:
- If you mount the data and config folders for a docker container you can skip backing up the container itself and back up the mounted folders with bog-standard backup tools. Recovery then means verifying the mount positions in the docker-compose file and running `up` on the new host
- When running cron (I also use separate cron containers as it’s been the cleanest and most stable solution), there are two handy tools:
- have the cron container use the image from the application itself: `image: nextcloud-app:latest` (easiest if you use a Dockerfile for the “base” image, even if it only contains `FROM nextcloud:stable`)
- use extension fields (https://stackoverflow.com/a/59796964)
Here are some I can share back:
- If you mount the data and config folders for a docker container you can skip backing up the container itself and back up the mounted folders with bog-standard backup tools. Recovery then means verifying the mount positions in the docker-compose file and running `up` on the new host
- When running cron (I also use separate cron containers as it’s been the cleanest and most stable solution), there are two handy tools: