I have just really started maintaining multiple instances of CFMX on one
server and I had an idea for how to do updates easier (hot fixes and
security updates). I'd like to know what your opinions are.
I started out with a master copy of the cfusion\cfusion-ear directory that I
use to make all of my instances. (based on the excellent blog/article by
Brandon Purcell).
Now, what I'm planning to do is apply all hot fixes/security patches to that
master copy. Then all new instances will have the patches when the instance
is created.
To fix the instances that were already created, I am planning to copy files
from the master that are newer than the files in the instance (after
stopping the instance of course) and then restart the instance.
What do you think? Does this seem sound?
Another question, when Macromedia puts out an updater for CFMX6.1, how
should it be done? Do you have to only run it once for all of the instances
or will it have to be run for each instance? I'm thinking that running for
each instance might make more sense that way you could upgrade different
instances at different times and make sure that the people in charge of the
instances have time to prepare.
Thanks for any opinions/comments.
Steve
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
