Where Does Spacebar Server Store Config and Data?
Spacebar server keeps its JSON config wherever CONFIG_PATH points, with keys and uploads in the data volume beside it.
Last updated
Spacebar splits config from state cleanly. One JSON file holds endpoints, database URLs, and feature flags, located by the CONFIG_PATH variable. The data volume beside it accumulates jwt keys, uploads, and runtime files.
Message history itself lives in PostgreSQL, so file backups alone under-restore. Snapshot the volume and dump the database together, and keep config out of public repos since it carries secrets.
Where Spacebar stores this, by platform
./data (Spacebar volume: config.json, keys, uploads)
config.json (via CONFIG_PATH) plus jwt keys and uploads in the ./data bind. History is in Postgres; back up volume and database dump together.
Frequently asked questions
How do I migrate a Spacebar server?
Copy the data volume (config.json, jwt keys, uploads) plus a Postgres dump to the new host, then start the stack with matching env. Re-point domain endpoints in config afterwards.
Where is the Spacebar config file?
Set CONFIG_PATH to the file location in the environment before starting. The Docker images generate a fresh config.json into the data bind on first run.
Notice an outdated path? Let us know.