Procédure de sauvegarde

Services

Note

As of 25/08/08 → 20 GiB approximatly. It should not grow very fast, since it is mostly configuration files and a text wiki.

Media is backed up seperatly where necessary:

  • jellyfin
  • navidrome

Dokuwiki

How to backup Dokuwiki ? → dokuwiki.org

Dokuwiki being a flatfile wiki, we can back it up by simply copying the /mnt/data/dokuwiki folder.

Jellyfin

Backup and Restore → jellyfin.org

Stop the container completly, then copy the config folder (maybe nothing else ?) → /mnt/data/jellyfin/config

Kavita

Backups → wiki.kavitareader.com

Backups are already generated, in /mnt/data/kavita/config/backups.

Automated Backup → navidrome.org

Backup can be automated via config file or env variables. Location is /mnt/data/navidrome/backup.

Miniflux

FAQ → miniflux.app

postgresql dump restore → postgresql.org

Miniflux stores all it's data in the postgresql db. We can dump it:

sudo bash -c "docker compose exec db pg_dump -U miniflux miniflux" > miniflux_backup.sql

And use the file to restore it later.

Readeck

Backups → readeck.org

docker exec -i readeck sh -c 'readeck export "/readeck/readeck_backup_$(date +%Y%m%dT%H%M%S).zip"'

to import, do the same and specifying the config file.

Needs to be recuring via cron job or script. Could also be built by script that does the overall backup, since backup is quick.

Caddy

It is sufficient to backup the /mnt/data/caddy. The most important folders inside are:

  • ./Caddyfile
  • ./html/

To restore, the both should be in the same folder, for the Caddyfile contains the paths to the different root folders for the websites hosted.

Missing or broken installs

  • archivebox
  • bookstack
  • etherpad
  • synapse
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9