A friendly place for programming greenhorns!
Big Moose Saloon
Register / Login
Win a copy of
Node.js in Action
this week in the
EJB and other Java EE Technologies
Best practices for configuration for staging environments
Joined: Oct 07, 2009
Oct 09, 2012 03:46:44
In a department meeting we had a discussion on changing our methods on addressing staging environments.
Up to now we generated a deployable for each staging environment (e.g. DEV, QA, PROD). From now on we want to generate one deployable and load the configuration file at runtime.
Is that the right way to go? Does it really bring along additional flexibility?
Also, a good how to/best practices guide would be very much appreciated.
Thanks in advance! - LX
I agree. Here's the link:
subject: Best practices for configuration for staging environments
logging version number at runtime
cvs best practices?
Java Developer, Cincinnati, OH 11/11/07
Loading Configuration files
All times are in JavaRanch time: GMT-6 in summer, GMT-7 in winter
| Powered by
Copyright © 1998-2014