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

[Backend] Setup environment variables for staging (dev vs prod) -- Investigation and Implementation #37

Open
3 tasks
bglossner opened this issue Feb 19, 2022 · 0 comments

Comments

@bglossner
Copy link
Collaborator

We are going to want to switch out certain things in our app based on the environment.

For now, you can just make this change based on the port. This will change later but this is good enough for testing.

Here's an example search that may yield stuff that's useful: "node express backend environment variables prod vs dev" -- https://www.google.com/search?q=node+express+backend+environment+variables+prod+vs+dev&rlz=1C1CHBF_enUS798US798&oq=node+express+backend+environment+variables+prod+vs+dev&aqs=chrome..69i57j33i160l2j33i299.56115j0j7&sourceid=chrome&ie=UTF-8

NOTE: We do want this to be "correct" in a sense so it's worth spending the time investigating for the best solution. Please write down any findings on things that do work and don't work and pros/cons of different approaches and why we want to use the way you have suggested. It's fine if this write up is short... because React recommends it officially is totally ok for a reason.

  • Investigation
  • Documentation
  • Implementation
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

No branches or pull requests

1 participant