Where Does sysPass Store Config and Vaults?
sysPass keeps app config plus backups in dedicated volumes with vaults in MariaDB. Persist all three or updates wipe you.
Last updated
sysPass splits into three volumes plus env. The config volume (app/config) holds connection and application settings written at install. The backup volume holds local database dumps. MariaDB holds encrypted vaults. Compose examples wire all three with fixed names; the app container publishes web ports while the db container stays internal.
Images track Debian/PHP generations, so pin versions deliberately and read the docs for your release line. Old 2.x/3.x guides reference paths that moved across majors. Keep credentials out of shell history when provisioning; the installer writes them into config on first run, after which the file owns the truth.
Where sysPass stores this, by platform
syspass-config (app/config volume)
Connection plus app settings, installer-written. Back with the backup volume and db dump as one unit. Images track Debian/PHP gens; follow your release line docs.
Frequently asked questions
how do i back up syspass
Copy the config volume (app/config), backup volume, and a MariaDB dump with containers stopped. Vaults travel encrypted in the db; connection and app settings in config. Restore all three together.
which syspass volumes are mandatory
Mount syspass-config, syspass-backup, and syspass-db persistently from day one. The compose file defines all three; skipping any one loses settings, local backups, or vaults respectively on recreate. Verify mounts before first login.
Notice an outdated path? Let us know.