![]() The status code of duplicacy backup will be provided in the firstĪrgument ( $1) in the post-backup script. You can return a non-zero code in pre-backup script to inhibit the If you specify either pre- or post-backup scripts, it will disable the scripts/post-backup.sh so they will get invoked accordingly. Is there any way we can get this into a docker image I’m fairly religious about running my web apps in docker images (reverse-proxied by Traefik). Note: I am running duplicacy on a Linux 圆4 server. ![]() Mount your scripts at /scripts/pre-backup.sh or First of all - nice work Soon you’ll be able to differentiate Duplicacy from other backup tools on the basis of performance AND functionality/ease of use. ![]() You can provide pre/post-backup scripts that runs before and after theīackup. If provided it will generate the pre/post-backup script automatically. Pruning will not run if this environment variable is not set. You can customize the behavior using the following environment variables: variableĭefault cron-like spec on when to run cron-like spec on when to run prune. Then docker-compose up -d to start the service. You can customize it with environment variables, see the Customization section. run.shis scheduled using cron (once a day for me choose whatever frequency fits you mood): /bin/bashset -eif EUID -ne 0 then >&2 echo 'This script must be run as root. LocalSettings.php:/data/LocalSettings.php:ro I’ve been running duplicacy in docker on my home server for quite a while now, and happy about it. preferences:/data/.duplicacy/preferences # mount files/directories below /data as readonly duplicacy_store:/data # mount the preferences file duplicacy_remote:/dest # base directory, any files mounted below /data will be included in the backup # mount remote position, which is not needed if you use a storage other than local folder Image: shouya/duplicacy-autobackup:latest environment: Suppose you have the following docker-compose file for a sample mediawiki service: You may want to initialize the repo in different ways other than those limitedly supported by the scriptĪs a result, you need to initialize the backup repository manually outside Docker, and then directly provide duplicacy’s preferences file via a mount.The image is tidier, and using the image doesn’t require as many environment variables.In this project, docker-duplicacy, I intentionally dropped the initialization feature, for two reasons: I also added support for hooks and healthchecks.io reporting. report to healthchecks.io with status and logsĬhristophetd/duplicacy-autobackup implemented the periodic backup feature.īased on which I forked shouya/duplicacy-autobackup, which bumped the version of duplicacy and converted the base image to s6 to support running the jobs non-root users. ![]() Understanding of basic usage of duplicacy is expected. This Docker image contains a daemon that backup files using duplicacy. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |