Where Does Self-Hosted revoltd Store Data?
Self-hosted revoltd keeps config in its own files while messages live in MongoDB, so both halves need backups.
Last updated
revoltd is only the backend piece: configuration files describe your instance while MongoDB holds users, channels and messages. Backing up one half without the other gives you a server that starts and remembers nothing.
Most installs run from a compose directory you created, so paths follow your setup rather than a fixed location. The database volume plus the config and secret files form the complete backup set.
Where revoltd stores this, by platform
./revolt/mongodb
Example MongoDB volume path holding all chat data, relative to your compose project. Your config files and secrets sit beside it in the project directory. Back up the volume with mongodump and copy the project files together.
Frequently asked questions
how do i back up a self-hosted revolt instance
Dump MongoDB with mongodump against the revolt database and store the dump plus your compose project files, configs and secrets, somewhere off the server. Either half alone is useless for a restore.
where is the revoltd config file
In your deployment directory, wherever you cloned or wrote the compose setup, not in a system path. Keep it with the database dump so a rebuild reproduces the same instance.
can i move revoltd data to a new server
Yes. Copy the project files over, restore the MongoDB dump into a fresh database container, and start the stack. Keep secrets identical or tokens and sessions invalidate.
Notice an outdated path? Let us know.