elpatron/cat-sitting-planner
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update README

Browse Source
This commit is contained in:
elpatron
2026-01-12 21:59:05 +01:00
parent a5a7df27cb
commit b3b1e0a75f
1 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
README.md
View File

@@ -28,16 +28,16 @@ The easiest way to host the Cat Sitting Planner is via Docker.
docker-compose up -d --build docker-compose up -d --build
``` ```
### 2. Persist Data ### 2. Persist & Backup Data (Important)
The database is stored in `/app/data/dev.db` inside the container. To persist your plans and bookings, map a volume to `/app/data`: All coordination data is stored in a single SQLite file at `/app/data/dev.db` inside the container.
**Example `docker-compose.yml` volume:** To ensure your plans are safe:
```yaml 1. **Always map a volume** to `/app/data`.
volumes: 2. **Backups**: Simply copy the `dev.db` file from your host path (e.g., `/mnt/user/appdata/csp/dev.db`).
- ./data:/app/data 3. **Upgrades**: As long as the volume mapping stays the same, your data will survive container updates.
``` 4. **Moving Systems**: If you move the app, copy your existing `dev.db` into the new host data folder **before** starting the container.
If you are using Unraid or a custom path: **Example `docker-compose.yml` volumes:**
```yaml ```yaml
volumes: volumes:
- /mnt/user/appdata/csp:/app/data - /mnt/user/appdata/csp:/app/data