Where Does Stump Store Its Data?
Stump reads Stump.toml from its config dir and keeps stump.db beside it. Docker mounts that dir at /config; libraries mount at /data.
Last updated
Stump centers on a config directory holding Stump.toml (port, library paths, auth, scanner options) and the stump.db SQLite database with users, libraries, and reading progress. Bare installs default to ~/.stump, overridable with STUMP_CONFIG_DIR. Docker sets that variable to /config and binds a host folder there.
Libraries stay outside in a /data mount (or wherever your paths point). That split makes backups one folder: copy the host directory behind /config and the whole server definition travels. Environment variables override any TOML value, which helps for secrets in compose without editing the file.
Where Stump stores this, by platform
/config (Docker volume)
Stump.toml plus stump.db (database defaults beside the config unless STUMP_DB_PATH moves it). Bind to a host folder. Library media mounts separately at /data and needs no app backup.
Frequently asked questions
how do i back up stump
Copy the whole mapped /config folder (Stump.toml plus stump.db) with the container stopped. Remount your library folders at the same /data paths. Reading progress and users travel in the database, so the file alone restores nothing.
is stump stable enough to self-host
Yes, and expect some. Stump is pre-1.0 beta software with occasional breaking changes. Pin image tags, read release notes before updating, and keep the /config backup current.
Notice an outdated path? Let us know.