Backups and keys
Back up /config and /data together. The library itself is Audiobookshelf’s to back up.
| What | Where | If you lose it |
|---|---|---|
| Database | /config/armarium.db |
Everything Armarium knows is gone: people, requests, history, settings. Books on the shelf are untouched. |
| Secrets key | /config/secrets.key |
The saved Audiobookshelf API key, Discord webhook and single sign-on secret can’t be read; enter them again. |
| Libation master key | LIBATION_MASTER_KEY, or /config/libation-master.key |
Every member has to connect Audible again. |
| Session key | ARMARIUM_SESSION_SECRET, or /config/session.key |
Everyone is signed out. Nothing else is lost. |
| Members’ Libation data | /data/users/*/libation |
Members connect Audible again; their requests and the shelf are unaffected. |
Server → This server lists the three keys and where each one lives on your install.
Keys from the environment or from files
Section titled “Keys from the environment or from files”The setup wizard puts LIBATION_MASTER_KEY and ARMARIUM_SESSION_SECRET in your .env. If they
aren’t set, Armarium creates libation-master.key and session.key in /config on first start and
uses those. Either way works; just keep .env in your backups if that’s where they are.
secrets.key is always a file. Keep it with armarium.db: a copy of the database without it can’t
reveal the secrets inside.
Restoring
Section titled “Restoring”Stop Armarium, put /config and /data back, start it again. Use the same image version you backed
up from, or a newer one: migrations only go forward.