A long while ago, I commented on having separate environments for test, production and development. This is one of those things, that need to be considered for whatever solution is being examined. If you have an opensource app you are testing, a place to do it is a good thing. If you are installing a CD that all of a sudden has Tomcat installed on the webserver. Maybe a separate box is best.
In developing there is logic that can be placed within code to have the application set up in which stage.
For example in MachII setting the development reloading can be as easy as
<--- Set the configuration mode (when to reload): -1=never, 0=dynamic, 1=always --->
<cfset request.isProductionMode = (listContainsNoCase(CGI.SERVER_NAME, "ProductionServerName")) />
<cfif not request.isProductionMode and structKeyExists(URL,"reloadApp")>
<cfset MACHII_CONFIG_MODE = 1 />
</cfif>
Its a neat trick for reloading and setting up the environments.
This is customized from the download on mach-ii.info
Subscribe and Share!
Did you enjoy this article? Your feedback is very important! I'd like to invite you to keep up to date with the latest posts from Anticlue. We offer several venues. If you have some questions, help can be found here.- Become a Facebook Fan
- Subscribe to Anticlue
- Follow me on Twitter
- Add to Technorati Favorites
- Digg this post
0 Comments to “Setting up things in production”
Please share your thoughts and suggestions
-
Receive Our eNewsletter
The latest Project Management and Healthcare IT practices
-
About Me
Welcome to the Healthcare IT Project Management Blog of Elyse Nielsen. This is the place where I share the ideas I have learned, the things I’d like to remember, and my thoughts for a brighter future. Find out more.
Subscribe to Our Tips
This weblog is licensed under a Creative Commons License.