Signer on Docker - Persistent data (backup considerations)
The standard Docker compose file for Signer uses two volumes:
- sql: database files
- files: files stored outside of the database (to keep the database tidy)
note
The sql and files volumes will probably be mapped by your container orchestrator to the automatically created volumes signer_sql and signer_files
Feel free to alter these volumes according to your infrastructure, for instance mapping them to folders on the host.
The stack also uses two secrets, generated manually during the setup:
- signer_sql_password: SQL server SA password
- signer_encryption_key: encrypts secrets such as session states
These two volumes and two secrets contain all data needed to recreate the Signer stack. No additional data is persisted inside the containers, and the stack may be recreated freely at any time.
caution
On a production environment, make sure you take the necessary steps to backup these resources!