Blame

1d634d admin 2025-09-03 14:28:17
added initial page
1
# Procédure de sauvegarde
2
3
## Services
8da001 admin 2025-09-03 14:29:02
added tip styling
4
> [!NOTE]
69cfe3 admin 2025-09-03 14:29:18
more styling
5
> As of _25/08/08_ → **20 GiB** approximatly. It should not grow very fast, since it is
8da001 admin 2025-09-03 14:29:02
added tip styling
6
> mostly configuration files and a text wiki.
1d634d admin 2025-09-03 14:28:17
added initial page
7
8
Media is backed up seperatly where necessary:
9
10
- jellyfin
11
- navidrome
12
4ae2a9 admin 2025-09-03 18:11:23
change dokuwiki section to otterwiki
13
### Otterwiki
1d634d admin 2025-09-03 14:28:17
added initial page
14
4ae2a9 admin 2025-09-03 18:11:23
change dokuwiki section to otterwiki
15
OtterWiki being a flatfile wiki, we can back it up by simply copying the
16
`/mnt/data/otterwiki` folder.
1d634d admin 2025-09-03 14:28:17
added initial page
17
094334 theophile 2025-09-28 20:49:23
initial forgejo backup documentation
18
### Forgejo
19
20
[Based on the documentation](https://forgejo.org/docs/latest/admin/upgrade/#backup), we only need to run
21
22
```bash
23
docker compose exec forgejo forgejo dump
24
```
25
1d634d admin 2025-09-03 14:28:17
added initial page
26
### Jellyfin
27
28
[Backup and Restore → jellyfin.org](https://jellyfin.org/docs/general/administration/backup-and-restore)
29
30
Stop the container completly, then copy the config folder (maybe nothing else ?)
31
`/mnt/data/jellyfin/config`
32
33
### Kavita
34
35
[Backups → wiki.kavitareader.com](https://wiki.kavitareader.com/guides/admin-settings/tasks/#kavita-backup)
36
37
Backups are already generated, in `/mnt/data/kavita/config/backups`.
38
39
### Navidrome
40
41
[Automated Backup → navidrome.org](https://www.navidrome.org/docs/usage/backup/)
42
43
Backup can be automated via config file or env variables. Location is
44
`/mnt/data/navidrome/backup`.
45
46
### Miniflux
47
48
[FAQ → miniflux.app](https://miniflux.app/faq.html#backup)
49
50
[postgresql dump restore → postgresql.org](https://www.postgresql.org/docs/current/backup-dump.html)
51
52
Miniflux stores all it's data in the postgresql db. We can dump it:
53
54
```bash
55
sudo bash -c "docker compose exec db pg_dump -U miniflux miniflux" > miniflux_backup.sql
56
```
57
58
And use the file to restore it later.
59
60
### Readeck
61
62
[Backups → readeck.org](https://readeck.org/en/docs/backups)
63
64
```bash
65
docker exec -i readeck sh -c 'readeck export "/readeck/readeck_backup_$(date +%Y%m%dT%H%M%S).zip"'
66
```
67
68
to import, do the same and specifying the config file.
69
70
Needs to be recuring via cron job or script. Could also be built by script that
71
does the overall backup, since backup is quick.
72
73
### Caddy
74
75
It is sufficient to backup the `/mnt/data/caddy`. The most important folders
76
inside are:
77
78
- `./Caddyfile`
79
- `./html/`
80
81
To restore, the both should be in the same folder, for the Caddyfile contains
82
the paths to the different root folders for the websites hosted.
83
5f0d87 theophile 2025-10-04 11:59:42
openwebui backup instructions
84
### OpenWebUI
85
86
We do not backup the `ollama` models. We only handle the `openwebui` data.
87
88
89
- [Backing Up Your Instance - openwebUI docs](https://docs.openwebui.com/tutorials/maintenance/backups/#scripting-a-backup-job)
90
91
92
**Dir structure**:
93
```
94
├── audit.log
95
├── cache/
96
├── uploads/
97
├── vector_db/
98
└── webui.db
99
```
100
1d65de theophile 2025-10-04 12:00:32
format improvement to openwebui section
101
1. Cold backup approach - Stops the container before backup for data integrity
102
2. Copies the entire `/webui` folder including:
103
- webui.db (main database with chats, users, settings)
104
- uploads/ (uploaded files)
105
- cache/ (cached data)
106
- vector_db/ (RAG/Knowledge embeddings)
5f0d87 theophile 2025-10-04 11:59:42
openwebui backup instructions
107
108
1d634d admin 2025-09-03 14:28:17
added initial page
109
## Missing or broken installs
110
111
- archivebox
112
- bookstack
113
- etherpad
114
- synapse