Apparently I changed the problematic for loop on the VM, but I forgot to copy the script back to the git folder before committing. I put the for loop into the IF branches now.
TESTING IS UNDERWAY - I will comment again once it is 100% verified working (for me, again, sorry.)
I tested it in Virtualbox with my own live server backups and it seemed to restore fine like this. I'm not sure if the help/explanation is enough, feel free to add more, change wording, etc.
This adds a "help" text, so the user knows their options. Calling just the script will now tell the user to either user 'backup', 'restore', or 'help'.
* Change default HTTP_BIND, HTTPS_BIND
https://github.com/mailcow/mailcow-dockerized/issues/4315#issuecomment-1083034329
* [Compose] Removed Colon after fallback IP in docker-compose.yml
* [Compose] Remove bind options from volumes (#4577)
(cherry picked from commit 4d53216c05)
* Migration (partially) of update.sh + cold-standby.sh to composev2
* Migration of update.sh + cold-standby.sh to composev2
* Migration of update.sh + cold-standby.sh to composev2
* Migration of update.sh + cold-standby.sh to composev2
* [ClamAV] Fixed ClamAV start before unbound
* Migration of update.sh + cold-standby.sh to composev2
* Formulation and values adjusted (IPv4 bind in generate-config.sh)
Co-authored-by: Amin Vakil <info@aminvakil.com>
Co-authored-by: qupfer <github@qupfer.de>
Co-authored-by: FreddleSpl0it <patschul@posteo.de>
* Fix restore script not restoring MySQL database on restore
* Add missing 'type' and 'maxdepth' options to 'find' command in backup and restore script
The verbose option dumps a progress percentage to `STDERR`. I'm piping `STDOUT` to `/dev/null` in my backup cron job but I'd like to keep `STDERR` in case something goes wrong. However because the progress gets dumped to `STDERR` by gzip it means it will always look like something went _wrong_.