Yes, that's what I was thinking. I mentioned in a response
a moment ago, the idea of using an entirely separate local
development environment, including all data and assets, from
everything on the development environment, and, in turn, from
the production environment.
Local:
127.0.0.1 local.site01.com
127.0.0.1 local.site02.com
Development Server:
(I would only have to setup the domains below in IIS. All code
and assets would mimic the local setup)
dev.site01.com
dev.site01.com
Production Server:
(At this level, all code is uploaded, and all client data and
assets are entered by the client through a management interface,
so even database values are not shared between local/development
and production environments. That's always a pain when I'm using
client data or assets locally and the client is also uploading
data or assets to the production server and I'm trying to make
sure I don't overwrite their data or assets...)
www.clientDomain01.com
www.clientDomain02.com
Does this follow your thinking?
(and don't be talking 'bout my mama! ;o)
Rick
-----Original Message-----
From: Eric Cobb [mailto:cft...@ecartech.com]
Sent: Thursday, February 24, 2011 9:20 AM
To: cf-talk
Subject: Re: I think I'm confused...
You can make up whatever entries you want in your hosts file, and it
will work on your local machine.
127.0.0.1 test1.loc
127.0.0.1 test2.loc
127.0.0.1 test3.loc
127.0.0.1 yo.mama
127.0.0.1 my.mama
127.0.0.1 free.beer
Whatever you want. I would recommend NOT adding host entries for actual
sites that you want to really pull up in the browser (your dev server,
production sites, etc...) as it really just becomes a pain having to
switch back and forth/.
Thanks,
Eric Cobb
ECAR Technologies, LLC
http://www.ecartech.com
http://www.cfgears.com
On 2/24/2011 7:00 AM, Rick Faircloth wrote:
> I could easily see that working for single sites,
> but if I'm developing a "multiple sites, one codebase"
> application that depends on reading specific domain
> names for setting sites variables, that means I have
> to have those dev.mydomain domains in the local hosts
> file, as well.
>
> I could just use the "mydomain" part of the url for
> identification, but as someone pointed out earlier
> in the MSOC discussion, that wouldn't account for
> subdomains, if they're used, such as blog.mydomain, etc.
>
> Any thoughts on this concern?
>
> Rick
>
>
> -----Original Message-----
> From: Mike Kear [mailto:afpwebwo...@gmail.com]
> Sent: Thursday, February 24, 2011 6:04 AM
> To: cf-talk
> Subject: Re: I think I'm confused...
>
>
> I use different domain names. I have www.mydomain.com for the live
> server site, and dev.mydomain for my local development sites
>
> Then in my hosts file, i have the line:
>
> 127.0.0.1 dev.mydomain
>
> for each client site i have. With apache, the local dev versions and
> remote server versions behave in an identical manner
>
> Cheers
> Mike Kear
> Windsor, NSW, Australia
> Adobe Certified Advanced ColdFusion Developer
> AFP Webworks
> http://afpwebworks.com
> ColdFusion 9 Enterprise, PHP, ASP, ASP.NET hosting from AUD$15/month
>
>
>
> On Thu, Feb 24, 2011 at 9:21 PM, Rick Faircloth
> <r...@whitestonemedia.com> wrote:
>> Ok... thanks Mark and Eric
>>
>> We need a better solution available to developers
>> to be able to switch between local and server DNS.
>>
>> Perhaps, a switch of some kind that could be inserted
>> into a URL to tell a browser to use a local hosts file
>> if that switch is present.
>>
>> http://local/www.xyz.com
>> or
>> http://l:www.xyz.com
>>
>> That would certainly be a *lot* easier than constantly
>> editing that hosts file.
>>
>> But it's good to know that I can use a local DNS file
>> that way!
>>
>>
>>
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
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:342568
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
