What’s a good way to explain that system configuration at run time should not be changed by code at compile time? [closed]
Closed 8 years ago.
Project configs for Java projects
How to store configs for project in Java. In normally case i stored it in ‘src/main/resources/’ with *.properties. How best approach for storing projects config for development, local, production environments?
Project configs for Java projects
How to store configs for project in Java. In normally case i stored it in ‘src/main/resources/’ with *.properties. How best approach for storing projects config for development, local, production environments?
Where would you put configurable data to minimize Change Management slow downs?
I want to start by saying I understand Change Management’s job especially when there are government contracts and security policies that must be followed. They are invaluable to prevent the mayhem that would ensue if devs were in control of prod.
Trade-off between locality and repetition
Let me explain what I mean by locality and repetition. The current crop of configuration management tools decouple the configuration from everything else even when it is somewhat detrimental to do so. One case where it is detrimental is in application configuration. I believe that application configuration should live in the same repository as the application itself instead of some other repository or a chef cookbook or a puppet module. Better yet the actual chef cookbook or puppet module should be alongside the application and the build system can figure out how to package the whole thing so that the deployment mechanism can be as simple as possible.
Should a 12Factor App persist config in the DB?
The 12factor approach to config is
In SemVer should I increase the version on every commit/accepted pull request
Running a community project. Have a few pull requests that have been made and the version of our product is currently 2.5.0
In SemVer should I increase the version on every commit/accepted pull request
Running a community project. Have a few pull requests that have been made and the version of our product is currently 2.5.0
What is the preferred way to store application configurations?
Most of the time, I store development application config in root directory of the project, like this: