Flow, accounts, and hosting
Configure self-hosted Duaer
Encryption keys, environment variables, databases, and task runners. Prefer Postgres in production and pin DUAER_ENCRYPTION_KEY.
Configuration entry points
- Encryption keys: credentials are encrypted at rest; every queue-mode worker needs the same key.
- Environment variables: process env, `.env`, or container injection.
- Supported databases: SQLite or Postgres.
- Task runners: internal or external runners.
- Configuration examples: copy-ready setups.
Questions
What should I configure first on self-hosted Duaer?
The encryption key, the database (Postgres in production), and the environment variables you will change. In queue mode every worker must share the same encryption key.
In this section
Hosting
Encryption keys in Duaer
Duaer encrypts credentials before saving them to the database. It creates a key on first launch; DUAER_ENCRYPTION_KEY overrides that.
HostingEnvironment variables for Duaer
Configure the self-hosted Duaer process with environment variables.
HostingSupported databases for Duaer
Self-hosted Duaer can use SQLite or Postgres.
HostingDuaer configuration examples
Copy-ready self-hosted configuration examples. Start with a custom encryption key.