Re: [ACFUG Discuss] Development vs Production Application.cfm and other things...

:* discussion@acfug.org > *Sent:* Wed, November 4, 2009 5:18:46 PM > *Subject:* RE: [ACFUG Discuss] Development vs Production Application.cfm > and other things... > > Good point. I did say I realized that ini files weren’t as “robust or > flexible”. :-) But WDDX files are definitely a

Re: [ACFUG Discuss] Development vs Production Application.cfm and other things...

n INI files, Wes. :-) /charlie From:ad...@acfug.org [mailto:ad...@acfug.org] On Behalf Of shawn gorrell Sent: Wednesday, November 04, 2009 1:29 PM To: discussion@acfug.org Subject: Re: [ACFUG Discuss] Development vs Production Application.cfm and other things... Let me throw yet another wrinkle int

RE: [ACFUG Discuss] Development vs Production Application.cfm and other things...

. :-) /charlie From: ad...@acfug.org [mailto:ad...@acfug.org] On Behalf Of shawn gorrell Sent: Wednesday, November 04, 2009 1:29 PM To: discussion@acfug.org Subject: Re: [ACFUG Discuss] Development vs Production Application.cfm and other things... Let me throw yet another wrinkle into the

Re: [ACFUG Discuss] Development vs Production Application.cfm and other things...

ssion@acfug.org" Sent: Wed, November 4, 2009 1:17:41 PM Subject: RE: [ACFUG Discuss] Development vs Production Application.cfm and other things... I use XML (as stated before) but for this single purpose, I agree with Charlie that it would be much simpler and just as affective

RE: [ACFUG Discuss] Development vs Production Application.cfm and other things...

From: ad...@acfug.org [mailto:ad...@acfug.org] On Behalf Of Charlie Arehart Sent: Wednesday, November 04, 2009 10:59 AM To: discussion@acfug.org Subject: RE: [ACFUG Discuss] Development vs Production Application.cfm and other things... Ajas, you mention some loving/some hating XML files. I didn'

Re: [ACFUG Discuss] Development vs Production Application.cfm and other things...

ying to stop you following the other approaches. Just want to make > sure folks are aware of the alternative. :-) > > > > /charlie > > > > *From:* ad...@acfug.org [mailto:ad...@acfug.org] *On Behalf Of *Ajas > Mohammed > *Sent:* Tuesday, November 03, 2009 8:42 PM >

RE: [ACFUG Discuss] Development vs Production Application.cfm and other things...

are of the alternative. :-) /charlie From: ad...@acfug.org [mailto:ad...@acfug.org] On Behalf Of Ajas Mohammed Sent: Tuesday, November 03, 2009 8:42 PM To: discussion@acfug.org Subject: Re: [ACFUG Discuss] Development vs Production Application.cfm and other things... Thank you everyone.

Re: [ACFUG Discuss] Development vs Production Application.cfm and other things...

Thank you everyone. The suggestions from everyone were very helpful. Using the suggestions helped me come across these links http://environmentconfig.riaforge.org/ http://learn.objectorientedcoldfusion.org/wiki/Managing_Multiple_Environment_Configurations

Re: [ACFUG Discuss] Development vs Production Application.cfm and other things...

I've been using Coldbox lately and have been making use of the environment control interceptors: http://ortus.svnrepository.com/coldbox/trac.cgi/wiki/cbEnvironmentControl Previously I had built what essentially amounted to the same idea by pulling in environment specific settings via xml onApplic

RE: [ACFUG Discuss] Development vs Production Application.cfm and other things...

PM To: discussion@acfug.org Subject: RE: [ACFUG Discuss] Development vs Production Application.cfm and other things... I like to keep the application.cfc the same and use an XML file to store the application variables and their values that differ on each machine. So, in the application.c

RE: [ACFUG Discuss] Development vs Production Application.cfm and other things...

I like to keep the application.cfc the same and use an XML file to store the application variables and their values that differ on each machine. So, in the application.cfc on application start, you can execute a component that can parse the XML and set application scope vars accordingly. Wes