Where Does Redash Store Queries and Config?
Redash keeps queries and dashboards in PostgreSQL with secret config in env files, while query results cache in Redis beside it, usually composed via Docker.
Last updated
Redash spreads state across three services by design. PostgreSQL holds queries, dashboards, and users durably. Redis caches results ephemerally. Environment files inject secrets and connection strings at boot.
Docker Compose papers over the complexity with named volumes for each piece. Backups target Postgres dumps plus env files while Redis gets a pass. Upgrades need matched image versions across web, worker, and scheduler containers.
Where Redash stores this, by platform
/opt/redash/env
Queries and dashboards in Postgres with secrets in env files. Redis cache rebuilds itself. Back up database dumps plus env.
Frequently asked questions
How do I back up Redash?
Dump PostgreSQL plus copy the env file with secrets, since queries live in rows not files. Redis cache rebuilds itself and skips backups. Version match the image tags on restore to avoid migration surprises.
Where does Redash configuration live?
Set database URL, secret key, and mail options in the env file the compose stack reads. Never commit real secrets beside the compose file. Rotate keys with downtime since sessions invalidate.
Notice an outdated path? Let us know.