> 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?
Well, it seems like a lot of work since you'll probably have already created
most of the instances before you install patches. Since you'll want to
update existing instances, I'd probably just recommend building a mechanism
that will allow you to do this.
> 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.
Although I'd personally prefer the former, I think, I suspect it'll have to
be run once for each instance for the reasons you mentioned.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
phone: 202-797-5496
fax: 202-797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
