This means we now need to have the text and HTML content set in the code, which is arguably better. In order to avoid allowing legacy Brevo API Key support, this will also introduce breaking changes and will be released as v2.0.0. I took the opportunity to remove a few deprecated things (like legacy ENV-based config), upgrade PostgreSQL, and pin a specific version in `docker-compose.yml`, since I don't plan to do breaking releases anytime soon, and upgrading PostgreSQL should be fine from now on if the version is pinned. If you were using Brevo with an API Key, they support SMTP as well, just update your config. If you were using ENV-based config, check `bewcloud.config.sample.ts`to create your `bewcloud.config.ts`. If you need help upgrading you PostgreSQL container, I've written a simple guide [step-by-step guide](https://news.onbrn.com/step-by-step-guide-upgrading-postgresql-docker-containers/).
21 lines
813 B
Plaintext
21 lines
813 B
Plaintext
PORT=8000
|
|
|
|
POSTGRESQL_HOST="postgresql" # docker container name or external hostname/IP
|
|
POSTGRESQL_USER="postgres"
|
|
POSTGRESQL_PASSWORD="fake"
|
|
POSTGRESQL_DBNAME="bewcloud"
|
|
POSTGRESQL_PORT=5432
|
|
POSTGRESQL_CAFILE=""
|
|
|
|
JWT_SECRET="fake"
|
|
PASSWORD_SALT="fake"
|
|
|
|
MFA_KEY="fake" # optional, if you want to enable multi-factor authentication
|
|
MFA_SALT="fake" # optional, if you want to enable multi-factor authentication
|
|
|
|
OIDC_CLIENT_ID="fake" # optional, if you want to enable SSO (Single Sign-On)
|
|
OIDC_CLIENT_SECRET="fake" # optional, if you want to enable SSO (Single Sign-On)
|
|
|
|
SMTP_USERNAME="fake" # optional, if you want to enable signup email verification or multi-factor authentication via email
|
|
SMTP_PASSWORD="fake" # optional, if you want to enable signup email verification or multi-factor authentication via email
|