Struggling with Pre and Post commande with Duplicacy Web 1.8.3

Support
#1

Hello,

After multiple hour trying my self, with Chat GPT, and the forum experience, still strugling in setting up the pre and post commande.

I am using Duplicacy in Docker with this volum monted :
volumes:
- /srv/xxxxxxx/duplicacy/config:/config
- /srv/xxxxxxx/duplicacy/logs:/logs
- /srv/xxxxxxx/duplicacy/cache:/cache
I have tried to put the pre and post scrip (tested manually they are working well ( to stop some specific container ):

in :

  • config/scripts
  • config/hooks

I do not have the “repositories” folders in the config folder, tried to create manually and the subfolder but still not working.

When i check the logs for an backup, i can see he is using the cach folder, but after the backup i canno find anything on this folder ( like the filters).

I have some Backup ID like :Backup_Raid3To or Backup_PAPERLESS ( no backup number here). if this can help

the pre-backuo script is :

Blockquote
#!/bin/bash

Exemple : stopper des conteneurs avant backup

containers=(“paperless-broker-1” " paperless-webserver-1" “paperless-db-1”)

echo “[Duplicacy scripts] Arrêt des conteneurs…”
for c in “${containers[@]}”; do
docker stop “$c”
done

#2

Which container? saspus’s? then /cache is what is mapped to .duplicacy_web/repositories. So you shall put your scripts to /cache/localhost/<number>/.duplicacy/scripts folder for backup, and into all subfolder for prune and other tasks.

If you use different container then refer to that container documentation or source.

References:

#3

Thanks, I have tried this also, in my picture here cache is the mounted volum for cache in the docker, i have put the scrips folder everywhere as you can see btu still cannot get the script running.

image
image946Ă—570 21.8 KB

What the mean ? ( in the WEB UI the backup ID are not number)
And yes I am using the Sapsus Container (thanks for this, you’r a god)

#4

Finally i switched from container to direct install on debian, and now it’s work. really dont know why i was struggling like that on the container.

1 Like
#5

Check that path to repositories under settings.json points to the right place. Also check that permissions of script files are correct. Does duplicacy see the script files?

This is far superior approach anyway. Duplicacy does not benefit from containerization really. It has no dependencies.

#6

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.