Managing complex configurations -
I would like to ask you for your opinion on a large number of campus (for example XML, .properties management practices) , Custom format etc.) Nowadays, configuration files come in many ways for counting in every more complex project.
How to not lose this kind of disturbance? How to reuse them the best way? Any good tool that can help (maybe some eclipse based)?
Obviously, the most fundamental task to do this is to put those configuration files into source control, Because they are actually a source code.
But the real challenge with configuration management is determining how many files are and how many replacements you have to do so that you can re-normalize the configuration of those design decisions and the very project- and environment -Versible, and can not make any device for you.
A common way is a master config file that has the default value and environment-specific files are only those configured values that are different for their environment, and which overwrite the default is an automated build process Is in the form of a part (which in fact you really should have).
Comments
Post a Comment