Privacy-first password manager with built-in email aliasing. Fully encrypted and self-hostable.
Update .env.example with postgres connection settings (#2238)
Leendert de Borst939380bcbae6
diff --git a/.env.example b/.env.exampleindex 5046594a1..a099ebc86 100644--- a/.env.example+++ b/.env.example@@ -29,6 +29,25 @@ SMTP_TLS_PORT=587# Whether to force redirect all HTTP traffic (80) to HTTPS (443). Defaults to true.FORCE_HTTPS_REDIRECT=true+# ===========================================+# DATABASE CONFIGURATION+# ===========================================++# By default AliasVault runs a bundled PostgreSQL container and the settings+# below already point at it (host "postgres" is that container), so you don't+# need to change anything.+#+# To use your own external PostgreSQL server instead (e.g. a managed instance or+# a dedicated database host), point these at your server and write its password+# to secrets/postgres_password. AliasVault and the install.sh db-export/db-import+# commands then use whichever database is configured here.+#+# The host must be a network address reachable from the containers.+POSTGRES_HOST=postgres+POSTGRES_PORT=5432+POSTGRES_DATABASE=aliasvault+POSTGRES_USER=aliasvault+# ===========================================# EMAIL SERVER CONFIGURATION# ===========================================