How about this: Your site: www.defaultwebsite.com Client site: www.myclient.com Client development site: dev.myclient.com
Setup your development sites to have hostheaders for the dev.myclient.com site. This would more closely mirror their site in production. - Calvin -----Original Message----- From: Rick Faircloth [mailto:[EMAIL PROTECTED] Sent: Monday, February 21, 2005 8:29 PM To: CF-Talk Subject: RE: How to set virtual sites for localhost viewing? >it's good to have your development environment mirror your production one as much as possible. For sure...that's what I've done in the past and trying to setup this time. It just takes some time to figure out the settings and procedures when things are setup differently... >In production, presumably, that client's content will have its own virtual server Yes, that's what I've done in the past...the idea of using a virtual directory was for an intermediate step between initial (for my eyes only) development and deployment of the finished site to the public. For the client to be able to access the site on the Internet, without using host headers for a virtual site (server), the website would have to be setup in a virtual directory under the default website so it could be accessed by domain name of the default website, e.g. http://www.DefaultWebsite.com/website/index.cfm, or by IP, e.g. http://66.xx.xx.xxx/website/index.cfm, right? That seems to be the only two ways I can get a site to show up without using the host headers and for those ways to work, I had to setup a virtual directory for the site and wait to setup a virtual site when I was ready to use the domain name with Host Headers... Am I understanding things or am I missing something? Rick -----Original Message----- From: Dave Watts [mailto:[EMAIL PROTECTED] Sent: Monday, February 21, 2005 5:33 PM To: CF-Talk Subject: RE: How to set virtual sites for localhost viewing? > The reason I don't go to a virtual server ("site" in IIS) at > first is to avoid having to use Host Headers and expose the > site to the public via the domain name before it's complete. > Usually, I would just tell a client to go > http://66.xx.xx.79/cfdocs/yoursite/index.cfm to view their site. > > Looks like that'll just change to telling to go to > http://www.DefaultWebsite.com/yoursite/index.cfm, which will > work the same, promote my website (when I finally build it!) > and be easier for the client to remember. > > Does this sound like it will work well? You don't have to expose anything to anyone you don't want to, whether you use virtual servers or not. I guess my whole point here is just to mention that it's good to have your development environment mirror your production one as much as possible. In production, presumably, that client's content will have its own virtual server, and won't be a directory within a virtual server. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:195903 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=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54