docker-compose backup issueshttps://gitlab.nettek.at/djeller/docker-compose-backup/-/issues2022-05-14T08:17:42Zhttps://gitlab.nettek.at/djeller/docker-compose-backup/-/issues/5Disable specific backups2022-05-14T08:17:42ZdjellerDisable specific backupsAdd the possibility to disable backups for specific docker-compose files / stacks.Add the possibility to disable backups for specific docker-compose files / stacks.https://gitlab.nettek.at/djeller/docker-compose-backup/-/issues/4Add dry-run2022-05-14T08:17:58ZdjellerAdd dry-runAdd possibility to dry-run both skripts to test if the settings are correct (config location, slack key,...)Add possibility to dry-run both skripts to test if the settings are correct (config location, slack key,...)https://gitlab.nettek.at/djeller/docker-compose-backup/-/issues/1Add restore script2022-05-14T08:19:31ZdjellerAdd restore scriptAdd a script that restores a given backup by
1) selecting the name from all available backups
2) selecting the snapshot
3) getting the volume names from inside the backup /volumes/ folder
4) restoring the backup contents with the volumes...Add a script that restores a given backup by
1) selecting the name from all available backups
2) selecting the snapshot
3) getting the volume names from inside the backup /volumes/ folder
4) restoring the backup contents with the volumes and configuration location mounted at the right name/place
Note: when running with `docker run --rm` anonymous volumes are deleted, named ones are not so the volumes restored continue to exist after the restic container stops running.