Where Does Gladys Store Data?
Gladys keeps SQLite state in Docker volumes with host paths per compose. Time-series filenames stay unverified.
Last updated
Gladys persists SQLite state in Docker volumes with host paths per compose file. Time-series companions stay filename-unverified across docs. Config flows through Web UI into the same database.
Host mounts vary while container spots stay fixed. DuckDB handles series beside SQLite state. Back up whole volumes rather than cherry-picked files.
Where Gladys stores this, by platform
/var/lib/gladysassistant
SQLite state with time-series companions in Docker volumes. Host paths vary per compose while container spots stay fixed. Time-series filenames unquoted.
Frequently asked questions
How do I back up Gladys?
Archive the host volume behind /var/lib/gladysassistant with database files inside. Compose examples vary host paths while container spots stay fixed. Time-series filenames stay unquoted for lack of sources.
SQLite versus DuckDB files?
They pair per role with SQLite for state and DuckDB for series. Exact series filenames lack verification across docs. Back up whole volumes rather than named files.
Where is the Gladys config file?
It configures through Web UI into the same database with host mounts deciding persistence. Env files carry ports and zones beside volumes. Dev docs confirm the stack without file lists.
Notice an outdated path? Let us know.