Where Does Self Hosted OpenSign Store Data?
Self hosted OpenSign stores uploads in the opensign-files volume and records in Mongo. Config comes from .env.prod beside compose.
Last updated
The OpenSign compose stack splits data three ways. Uploaded documents land in the opensign-files volume, mounted into the server container. Database records live in the Mongo data volume. All secrets and URLs come from the env file beside compose.
The sample Mongo is a known trap. Upstream notes the default instance is not persistent across restarts, so production setups point at a managed Mongo URL. The Caddy data volumes hold TLS state and can be rebuilt. Treat the env file as a secret: it carries mail keys and the signing passphrase.
Where OpenSign stores this, by platform
/var/lib/docker/volumes/opensign_opensign-files/_data
Uploaded documents and signing artifacts. This is the user payload. Back it up on its own schedule.
/var/lib/docker/volumes/opensign_data-volume/_data
Mongo records for users, documents, and audit trails. Point at your own Mongo URL for persistence.
/opt/opensign/.env.prod
Secrets, mail keys, and URLs loaded by every container. Copy the sample env file here and fill in real values.
Frequently asked questions
How do I back up self hosted OpenSign?
Back up the opensign-files and data volumes plus .env.prod together. The default Mongo in the sample stack is ephemeral, so wire your own connection string for keeps.
Why are my email attachments 0 KB?
Set the host URL variable before first start and keep server and public URLs consistent. Attachment bugs usually trace to mismatched internal and public addresses.
Notice an outdated path? Let us know.