>For instance, you can't easily use references like <img src="/images/abc.gif">.
That's true...my workaround has been to create variables for paths in my Application.cfm depending on what the CGI.Server_Name is. If your approach would allow me to avoid that chore for every new site, then it would be easier to manage the DNS (once I figured it out) than change the Application.cfm each time. Now, I've just figured out how to manage my DNS records with DNS server with GoDaddy.com within the last year...with what we're talking about here, is this just manipulation of the DNS records on my server only? (Showing my lack of understanding about DNS now...) Thanks for the tip... Rick -----Original Message----- From: Jim McAtee [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 23, 2005 3:00 PM To: CF-Talk Subject: Re: How to set virtual sites for localhost viewing? There can be a big difference between using a dedicated site and trying to accomplish the same thing by simulating a site within a subdirectory. For instance, you can't easily use references like <img src="/images/abc.gif">. I doubt you'll be managing DNS constantly, but it depends on how often you accept new client projects. If you have a client for whom you regularly work on their web site then you could always leave the virtual site client.ourdomain.com configured in DNS. The other thing you might do is create a fixed number of 'generic' development virtual web sites. test01.ourdomain.com test02.ourdomain.com ..... test20.ourdomain.com Create and leave the host names in DNS. One time and then forget about it. Set up the virtual sites within IIS and then stop/start them as needed. You'll probably want to implement a login system to view these sites while under development, even if they're intended to be publicly available sites. ----- Original Message ----- From: "Rick Faircloth" <[EMAIL PROTECTED]> To: "CF-Talk" <cf-talk@houseoffusion.com> Sent: Wednesday, February 23, 2005 12:03 PM Subject: RE: How to set virtual sites for localhost viewing? >I manage my DNS through GoDaddy.com, where I register my sites. > Haven't ventured into the land of managing my own DNS. > > After looking into this at GoDaddy, it seems simpler, just to use > a virtual directory under my DefaultWebsite for online development > viewing, > sending my client to http://www.DefaultWebsite.com/ClientSite, then, > once > the site is ready to go live, make a virtual site for it... > http://www.ClientSite.com > > Is that not easier than manipulating DNS constantly? > (It probably seems easier because I understand it! ;o) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:196179 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
