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

frontend/bin/env.js should use dotenv #3667

Closed
1 of 4 tasks
shubham-padia opened this issue Mar 26, 2024 · 0 comments · Fixed by #3668
Closed
1 of 4 tasks

frontend/bin/env.js should use dotenv #3667

shubham-padia opened this issue Mar 26, 2024 · 0 comments · Fixed by #3668
Labels
bug Something isn't working

Comments

@shubham-padia
Copy link
Contributor

How are you running Flagsmith

  • Self Hosted with Docker
  • Self Hosted with Kubernetes
  • SaaS at flagsmith.com
  • Some other way (add details in description below)

Describe the bug

Right now, frontend/bin/env.js does not pick up values from .env, and we need to set inline env variables to change the project environment (local/dev/prod)

Steps To Reproduce

ENV=local in .env would not change the project environment

Expected behavior

ENV=local in .env would change the project environment and run the project against local backend

Screenshots

No response

@shubham-padia shubham-padia added the bug Something isn't working label Mar 26, 2024
shubham-padia added a commit to shubham-padia/flagsmith that referenced this issue Mar 26, 2024
Fixes: Flagsmith#3667.
This helps us set project ENV in .env instead of needing to
declare it inline.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant