You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, we have many env vars that are redundant or not consistently named. Consider the following set of env vars for prod, as they appear in our application.template.yml file (below), where API_URL and BASE_PATH both point to the same value, as do NODE_ENV and ENV. Additionally, I had to add a REACT_APP_API_URL in #30.
I suspect this is owed to the merge of the BE and FE needing similar configs, and having different naming conventions. I propose consolidating where possible, and removing env vars if they have the same value across values (which is true of BASE_PATH and SWAGGER_ENDPOINT.
production:
NODE_ENV: production
ENV: production
PROXY_ENFORCE: false
PROXIED_API_URL: ''
PROXIED_API_TOKEN: ''
# === FE ===
API_URL: /api/v1
# === BE ===
# PORT
PORT: 8080
# LOG
LOG_FORMAT: prod
LOG_DIR: ../../../tmp
# CORS
ORIGIN: "*" # we'll want to limit CORS in prod once we have a domain
CREDENTIALS: true
# SWAGGER_SERVER_URL: http://localhost:3000
SWAGGER_ENDPOINT: /api-docs
# API
BASE_PATH: /api/v1
SERVER_STATIC_BUILD: 'true'
# DATABASE
DATABASE_URL: your-production-postgres-url
SHADOW_DATABASE_URL: your-production-shadow-postgres-url
The text was updated successfully, but these errors were encountered:
At the moment, we have many env vars that are redundant or not consistently named. Consider the following set of env vars for prod, as they appear in our
application.template.yml
file (below), whereAPI_URL
andBASE_PATH
both point to the same value, as doNODE_ENV
andENV
. Additionally, I had to add aREACT_APP_API_URL
in #30.I suspect this is owed to the merge of the BE and FE needing similar configs, and having different naming conventions. I propose consolidating where possible, and removing env vars if they have the same value across values (which is true of
BASE_PATH
andSWAGGER_ENDPOINT
.The text was updated successfully, but these errors were encountered: