Re: configuration management application
Mark Space wrote:
arimanni@gmail.com wrote:
If the project would be more complex, I would consider using a version
control system and storing separate branches for different
environments.
This actually sounds kind of yucky. Different branches are the same as
different source files. You probably don't want to maintain one source
file per environment. This sounds like a maintenance nightmare.
What you want is a single file that does everything, in any environment.
Then either configure it at runtime (some sort of config.xml in the
resource file, for example) or have a much smaller set of objects which
are specific to the environment, where your environment specific
behavior is encapsulated.
Using branches is just an invitation to make branches everywhere. You
don't want to do that.
Upthread the word "connection" was bandied about as a consideration.
There are five or six database systems out there that you can say, "Use one of
these" and not risk losing too many customers. Load all six drivers.
Add six configuration URLs to your properties files.
Cycle through all known ones when the application inits - if you haven't hit
one after list end, sound the klaxons.
Allow customers to install a db.properties file that specifies their oddball,
shoulda-gotten-Postgres discount-store piece o' De BMS, and scan said
properties file if present, and hey, presto!, you don't even need to sweat
those scenarios.
--
Lew