mirror of
https://github.com/mailcow/mailcow-dockerized.git
synced 2024-12-23 02:04:46 +02:00
7c8e5c10ca
This is related to https://github.com/mailcow/mailcow-dockerized/issues/5970 and https://community.mailcow.email/d/2126-backup-restore/2 It adds `docker compose create` to the script which gets executed directly after the sync of the mailcow-dockerized directory. This way the Docker daemon on the remote side creates everything and we get rid of the warning "volume "XYZ" already exists but was not created by Docker Compose. Use `external: true` to use an existing volume" This is helpful if you use the create-cold-standby.sh script to migrate your mailcow installation to another server and don't want to get those warnings after migration. Co-authored-by: Niklas Meyer <niklas.meyer@servercow.de> |
||
|---|---|---|
| .. | ||
| docker-compose.override.yml.d | ||
| _cold-standby.sh | ||
| add-new-lang-keys.php | ||
| backup_and_restore.sh | ||
| check_translations.rb | ||
| expiry-dates.sh | ||
| generate_caa_record.py | ||
| mailcow-reset-admin.sh | ||
| reset-learns.sh | ||
| update_compose.sh | ||
| update_postscreen_whitelist.sh | ||