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
{{ message }}
This repository has been archived by the owner on Jun 15, 2023. It is now read-only.
What are the best practices for handling environment specific builds with Brunch? For different environments (dev, staging, prod) I would like to include different configurations (client side). I also want to store the configuration files in version control, so I don't think that dotenv is a good option. All the different configurations should not be seen in the front end - only the one that is used.
This discussion was converted from issue #1810 on August 07, 2021 20:29.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
What are the best practices for handling environment specific builds with Brunch? For different environments (dev, staging, prod) I would like to include different configurations (client side). I also want to store the configuration files in version control, so I don't think that dotenv is a good option. All the different configurations should not be seen in the front end - only the one that is used.
Do you have any suggestions?
Beta Was this translation helpful? Give feedback.
All reactions