Where Does mStream Store Its Config?
mStream keeps config.json plus its database in a /config volume. Music mounts separately at /music and never needs app backup.
Last updated
mStream centers on config.json inside a /config volume: port, users and password hashes, folders, scan options, and federation settings. The database, album art, and waveform caches sit beside it in the same volume. Music itself mounts read-only style at /music, outside the backup scope.
LinuxServer images map host folders to /config and /music with PUID/PGID for ownership, which is the standard layout to copy for migration. Bare installs generate a default config at save/conf/default.conf instead, overridable with the -j flag. Either way the config volume is the unit: one folder holds identity, library index, and caches together.
Where mStream stores this, by platform
/config (Docker volume)
config.json plus database, art, and waveform caches. Set users and passwords here (v5 ignores legacy env vars). Mount persistently with matching PUID/PGID; /music beside it holds the actual files.
Frequently asked questions
how do i back up mstream
Copy the whole mapped /config folder (config.json, database, image and waveform caches) with the container stopped. Remount /music at the same path. Users, playlists, and federation keys travel in the config volume.
why did my mstream login break after v5
Yes. v5 requires config.json and ignores the old USER/PASSWORD/USE_JSON variables; v4 files get renamed to config.json.v4-bak on upgrade. Recreate users and passwords through the new file or the web admin after upgrading.
Notice an outdated path? Let us know.