James Buckingham wrote: > > I thought I'd do a bit of asking around as I don't seem to be able to > find much about this online. I'm curious about how others manage > things like updates, testing and release management on a daily basis > across multiple instances of CF running on more than one server.
We build EAR files in the build environment and move them from there to testing, QA and production. The configuration comes from properties files that are local to the server, instance or even application so typically we do not have to do any configuration on the server for an update (only when it is a feature release). We just shut the instance down, remove the old EAR file, drop the new one in and restart the instance with a batch file that in the process removes all the temp files of the previous EAR file. Typically takes 1 minute per instance, but in clusters we do the instances 5 minutes apart to allow the sessions to sync before we do the next instance. Someday I will automate this completely (the build environment is already automated), but for now we do the upgrades and checks manually. Jochem ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create robust enterprise, web RIAs. Upgrade & integrate Adobe Coldfusion MX7 with Flex 2 http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:266597 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
