Where Does Plume Store Posts and Uploads?
Plume stores posts in Postgres and uploads in static. Config lives in a .env file beside the binary.
Last updated
Plume is a federated blog engine. Article text and follows live in Postgres. Uploaded images and static assets live under static in the Plume working directory. Config comes from a .env file with database URL, domain, and keys.
Docker setups usually mount the working directory or static as a volume. For a full backup you need three things: the Postgres dump, the static folder, and the .env file. Pin the Plume and Postgres versions during the move, since federation keys depend on a stable domain and database.
Where Plume stores this, by platform
/opt/plume/static
Uploads and static files. Mount persistently in Docker. Copy recursively for migration.
/opt/plume/.env
Database URL, domain, and secrets. Lives beside the Plume binary or compose file. Back it up with the database dump.
Frequently asked questions
how do i back up plume
Dump Postgres with pg_dump, then copy the static uploads folder and .env file. Restore the dump on the new host before starting Plume. Keep the same domain to preserve federation.
where are plume uploads stored
Federated media and local uploads land under static. That folder must be persistent in Docker. The database alone is not enough for a full restore. Check the static path in .env if uploads 404 after a move.
Notice an outdated path? Let us know.