Skip to content

Backups and data

Robin Müller edited this page Aug 3, 2026 · 2 revisions

Backups and data

Smart Drink Fridge uses SQLite. No external database server is required.

Docker storage

The standard Compose setup stores the database in the persistent fridge-data volume and backups under ./backups.

Do not assume that deleting a container deletes its named volumes. Conversely, do not delete volumes unless you intentionally want to remove the stored data.

Create and restore backups

Open Settings, then use the backup section to:

  • Create a backup immediately
  • Download a backup
  • Restore a selected backup
  • Delete an obsolete backup
  • Choose the frequency, time, and day of week
  • Limit backups by retained count and maximum age in days

The schedule fields are arranged in two rows: timing in the first row and retention limits in the second. A maximum age of 0 disables age-based cleanup. New files use the language-neutral prefix smart-drink-fridge_. Older files whose names begin with getraenke_ remain compatible; Getränke is simply the German word for drinks.

Restoring replaces the active application database. Download an additional copy before a restore when the current state might still be needed.

Manual safety copy

Stop writes or stop the web/scanner services before copying the SQLite file manually:

docker compose stop web scanner

Then copy the relevant database or Docker volume using your normal host backup tooling, and restart:

docker compose up -d

Updates

Container recreation and normal image updates preserve mounted data. Always verify the mounts before switching between a manual docker run installation and Docker Compose because they may point to different database locations.

Clone this wiki locally