(refactor) make Docker backup root static in Django setup
Remove backup_root from the normal Django global config form and display the fixed container path /backups instead. Always persist /backups from the setup form so Docker deployments do not mix host paths with container paths. Update tests and docs to clarify that the host backup directory is chosen through the Docker mount, while Django always uses /backups internally.
This commit is contained in:
@@ -129,15 +129,15 @@ docker compose up --build web scheduler worker
|
||||
```
|
||||
|
||||
The container persists `/opt/pobsync` and the SQLite database in Docker volumes.
|
||||
Backup data is mounted at `/backups` inside the containers. By default this uses `./backups` on the host.
|
||||
Override it with `POBSYNC_BACKUP_ROOT`:
|
||||
Backup data is always available at `/backups` inside the containers. By default this uses `./backups` on the host.
|
||||
Override the host-side mount with `POBSYNC_BACKUP_ROOT`:
|
||||
|
||||
```
|
||||
POBSYNC_BACKUP_ROOT=/mnt/backups/pobsync docker compose up --build web scheduler worker
|
||||
```
|
||||
|
||||
In the Django global config, set the backup root to `/backups` when running in Docker. For local, non-Docker use,
|
||||
set it directly to the host path, for example `/mnt/backups/pobsync`.
|
||||
The Django setup UI keeps the backup root fixed at `/backups`; only the Docker mount decides which host directory
|
||||
that points to.
|
||||
|
||||
## Docker With MariaDB
|
||||
|
||||
|
||||
Reference in New Issue
Block a user