What I'm trying to accomplish (which perhaps has been slowly modified over the course of this thread :o) is setting up an easily maintained MSOC development environment for all levels; local, development, and production.
At first, I was thinking about perhaps needing to mimic actual client domains, but if the environments are completely separate in terms of variables, the domains actually used at all levels shouldn't matter. Your method would work, however, for using the actual domains involved on the client side locally, as has been proven by your successful deployment. -----Original Message----- From: Dain Anderson [mailto:[email protected]] Sent: Thursday, February 24, 2011 10:16 AM To: cf-talk Subject: Re: I think I'm confused... I was under the impression you were wanting to test different domain settings, locally, and the method I mentioned allows you to quickly switch between one domain to the next by just changing the aliased CGI variable. This approach has nothing to do with your hosts file though, so I'm not sure if we're on two different paths here. -Dain On Thu, Feb 24, 2011 at 9:59 AM, Rick Faircloth <[email protected]>wrote: > > > However, it doesn't avoid the manual entry of the above code for > every local domain name, does it? Or what am I failing to understand? > > Rick > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:342577 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
