@Jeff: Best practices aside... if you want to drop me a line at adrock at adobe dot com, we can get to the bottom of your CB config issue.
-Adam On Mon, Aug 16, 2010 at 6:44 PM, Ian Skinner <[email protected]> wrote: > > On 8/16/2010 3:29 PM, Andrew Scott wrote: > > Dave, > > > > I am sorry but if I install one, two, three instances and I wish to use > the > > very initial instance there should be no reason not to. I would like > someone > > to give me a very valid good reason why it is frowned upon? > > > > I might have one instance for one client, and another for another client. > > But why should I want the settings copied across to the second client? I > > don't, that's why I went with the instances, because I need them with > > separate settings per instance per client. > > That is the POINT! IF you use the initial cfusion instance for client B > today, then tomorrow create a new instance for client > D, ColdFusion is going to copy everything in the cfusion instance into > this new one, including all of client B's settings. > > So if this is something that you do not want. Then not using the > cfusion instance for any development is a best way to keep it clean so > that when it is copied to make new instances by ColdFusion, there will > be no unnecessary settings copied with it. > > Now, yes there might be times when you want this. For a time when we > had some common, universal Data sources and mappings that we wanted to > be the same in all our projects we put them into the cfusion instance to > be copied. But we didn't use it for actual projects. > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:336327 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
