Where Does Misskey Store Config and Data?
Misskey reads .config/default.yml for settings, with Drive files in /misskey/files and posts in PostgreSQL.
Last updated
Misskey configures by file, not environment. The .config/default.yml file holds the instance URL, database, and Redis endpoints, plus optional object storage and search. Drive uploads land in /misskey/files unless S3 takes over. Posts live in PostgreSQL, job state in Redis.
The URL deserves emphasis because newcomers miss it: it becomes federation identity on first boot and cannot change later. Volumes for postgres, redis, and files must all persist, or redeploys wipe different thirds of the server.
Where Misskey stores this, by platform
./.config/default.yml
Instance URL, DB, Redis, and optional S3 and Meilisearch blocks. Copy the docker example to default.yml and edit before first boot.
/misskey/files
Drive upload home. Mount persistently or redeploys wipe attachments while posts survive in the database.
Frequently asked questions
How do I back up a Misskey instance?
Back up the postgres volume, the files volume, and default.yml together. Files without rows are orphans, and rows without files are broken attachments.
Can I change the instance URL later?
You cannot. The URL is baked into federation identity at first boot. Pick the final domain before creating the admin account.
Misskey starts but federation is dead. What is missing?
Check that Redis runs and the config points at it. Timelines, notifications, and federation delivery all queue through Redis, so nothing works without it.
Notice an outdated path? Let us know.