Skip to content

Commit

Permalink
chore: use project-specific environment variables...
Browse files Browse the repository at this point in the history
- For now, the email fields are commented out. Not sure how best to handle case where environment variable is not present. Two possible solutions:
  1. Optimal solution - If environment variable is not present, see if returning a YAML boolean will prevent the env var from being set in the container
  2. Less-optimal solution - In Elixir code, cast empty string value to nil
  • Loading branch information
arcanemachine committed Sep 26, 2023
1 parent fd2a956 commit 933a0da
Showing 1 changed file with 5 additions and 7 deletions.
12 changes: 5 additions & 7 deletions support/containers/compose.phoenix.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -12,10 +12,8 @@ services:
# db
DATABASE_URL: "${DATABASE_URL:?}"

# email
AWS_REGION: "${AWS_REGION:?}"
AWS_ACCESS_KEY: "${AWS_ACCESS_KEY:?}"
AWS_SECRET: "${AWS_SECRET:?}"

# sentry
SENTRY_DSN: "${SENTRY_DSN:?}"
# # email
# AWS_REGION: "${AWS_REGION}"
# AWS_ACCESS_KEY: "${AWS_ACCESS_KEY}"
# AWS_SECRET: "${AWS_SECRET}"
# EMAIL_RECIPIENT_CONTACT_FORM: "${EMAIL_RECIPIENT_CONTACT_FORM}"

0 comments on commit 933a0da

Please sign in to comment.