Use specific files for different enviroments
See original GitHub issueIt would be awesome to have files for each environment (development, production, qa, etc) available on /config
, and to copy them just before running the server/compiling.
I am thinking on using different config.xml
, and also a static class storing API’s urls.
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
How to use different .settings files for different environments in ...
Basically, I want two separate Settings classes: the general Settings class that stores the selected environment and non-environment specific ...
Read more >Using multiple .env files. - Prisma
One solution is to have multiple .env files which each represent different environments. In practice this means you create a file for each...
Read more >A common way of managing configurations for multiple ...
This article intended to share ideas and solutions to address some challenges related to Configuration Management, especially in the cloud ...
Read more >Managing Multiple Configuration File Environments with Pre ...
Just create one config file, and use specific tags for items you wish to vary. Then let your build server change these, depending...
Read more >Applying portable properties files across multiple environments
Applying portable properties files across multiple environments. Use the wsadmin tool to extract a properties file from one cell, modify ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Looks good, I think the solution has to be a gulp script at the moment.
I keep being reminded (#131, https://github.com/lathonez/clicker/issues/38#issuecomment-239497285) that Ionic are moving back to webpack. Not sure what the setup is going to be after that with regard to gulp, but having environment specific config files and [insert task runner here] copying them at build time is the way to go.
Incidentally, our closed source project will be going to prod within the next couple of weeks, so we’ll need to address this ourselves.
If we deviate from the pattern above I’ll be sure to raise here for discussion.
For now I’d like to close this (I’ll add a link from the blog post). Is that OK with you or is there something else to cover?
#135 closed