silikonvilla.blogg.se - Duplicacy preference file

DUPLICACY PREFERENCE FILE CODE
DUPLICACY PREFERENCE FILE PASSWORD

You can click the tag name to go to the source on GitHub for that particular tag. Tags ¶ Where can I find the source of the image?

DUPLICACY PREFERENCE FILE PASSWORD

If you don't want to enter your password every time you restart the container, you can set the environment variable DWE_PASSWORD with your password or starting with version 1.4.1 a file /config/keyring will be created that stores your password encryted if you click the checkmark on the login page.

In most cases you'll need to add additional volumes, depending on your own personal preference, to get access to your files.

DUPLICACY PREFERENCE FILE CODE

The status code of duplicacy backup will be provided in the firstĪrgument ( $1) in the post-backup script.Version : "3.7" services : duplicacy : container_name : duplicacy hostname : duplicacy image : cr.v/hotio/duplicacy ports : - "3875:3875" environment : - PUID=1000 - PGID=1000 - UMASK=002 - TZ=Etc/UTC volumes : - /:/config - /:/cache - /:/logs 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. Mount your scripts at /scripts/pre-backup.sh or 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. LocalSettings.php:/data/LocalSettings.php:ro

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.