Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: add node_env env var to frontend #2609

Closed
wants to merge 3 commits into from
Closed

Conversation

BlairCurrey
Copy link
Contributor

@BlairCurrey BlairCurrey commented Mar 25, 2024

Changes proposed in this pull request

  • adds production nodeEnv to frontend

Context

fixes #2592

Depends on interledger/helm-charts#27 interledger/helm-charts#35 Will need to merge that first.

Checklist

  • Related issues linked using fixes #number
  • Tests added/updated
  • Documentation added
  • Make sure that all checks pass
  • Bruno collection updated

Copy link

netlify bot commented Mar 25, 2024

Deploy Preview for brilliant-pasca-3e80ec canceled.

Name Link
🔨 Latest commit d2d562e
🔍 Latest deploy log https://app.netlify.com/sites/brilliant-pasca-3e80ec/deploys/663a429e861c160008b71a05

@golobitch
Copy link
Collaborator

@BlairCurrey I also opened up PR in helm-charts repo to add nodeEnv variable in helm charts (exactly the same way as it is for backend and auth) so that we can specify this in values.yaml file when deploying helm.

interledger/helm-charts#27

@BlairCurrey BlairCurrey marked this pull request as ready for review May 7, 2024 14:12
@golobitch
Copy link
Collaborator

To be perfectly honest, this is not needed, since default value is set to production in helm-charts repository. I suppose that we can just close this PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fix frontend issue when running with NODE_ENV=development
2 participants