Ok...what I did at GoDaddy was entered "dev" along with "www" and "@" as A Records for ShellmanBluffOutfitters.com...
For the virtual website on my server, I put dev.ShellmanBluffOutfitters.com as Host Header...sound right? Rick -----Original Message----- From: Calvin Ward [mailto:[EMAIL PROTECTED] Sent: Monday, February 28, 2005 2:38 PM To: CF-Talk Subject: RE: How to set virtual sites for localhost viewing? If that's the case, then www.ShellmanBluffOutfitters.com would also be too long. Dev is exactly like www as far as setting up in DNS. CNames could be useful, but let's keep it simple until it is working! - Calvin -----Original Message----- From: Rick Faircloth [mailto:[EMAIL PROTECTED] Sent: Monday, February 28, 2005 1:08 PM To: CF-Talk Subject: RE: How to set virtual sites for localhost viewing? I tried setting up a subdomain at GoDaddy for dev.ShellmanBluffOutfitters.com, but it rejected it as too long...said it had to be under 25 characters. But would this dev domain be added as a subdomain or as another type of domain, like www, or @, in this case, being dev? (We're talking A Records, now) Or is this where CName's come into play? (I'm probably just complicating a simple issue... I seem to have a knack for that! ;o) Right now my server gets little enough traffic that it's not a problem to preview sites to clients. All my initial development is done on a laptop, apart from the server. Thanks for the tip on VMWare...I'll check that out! Rick -----Original Message----- From: Calvin Ward [mailto:[EMAIL PROTECTED] Sent: Monday, February 28, 2005 12:40 PM To: CF-Talk Subject: RE: How to set virtual sites for localhost viewing? You've got it right, up until you talk about changing the DNS from dev.clientsite.com to www.clientsite.com. I take it that your dev server is also your production server, in a perfect world, you wouldn't want it that way. But assuming that is the case, when the site is ready to go live, you would merely add the live site to your server. So after go live, you would have something like: www.clientsite.com serving D:\websites\clientsite\www dev.clientsite.com serving D:\websites\clientsite\dev (note: On a single physical server like this, I would actually do my path something like: D:\websites\clientsite\www\webroot, so that I could have non-web accessible content that belonged to that site available under paths like D:\websites\clientsite\www\files or such) Your client could always preview changes at dev (or any name you prefer really), and upon approval you can move those changes to www. At GoDaddy (how about that superbowl commercial?), you would have two DNS entries. You'll still have to test to see which site your app is running on. The benefit is that your dev and production sites are more closely mirrored, particularly in regards to the pathing discussion last week. For developing on your laptop, I recommend VMWare, you can check it out for free in their current beta. This will really allow you to emulate your other environments while disconnected! - Calvin -----Original Message----- From: Rick Faircloth [mailto:[EMAIL PROTECTED] Sent: Monday, February 28, 2005 12:25 PM To: CF-Talk Subject: RE: How to set virtual sites for localhost viewing? Hi, Calvin... Thanks for the tip...I'll look into doing it that way. Now, IIUYC (If I Understand You Correctly...(funny...my spellchecker tried to substitute "Idiocy" for IIUYC! It's probably more insightful than I want to admit! ;o) you're saying that that I would need to create a subdomain with GoDaddy.com, where I handle my DNS for my sites, and create a subdomain for each client that has a site under development? e.g. dev.ClientSite1.com dev.CleintSite2.com etc... Then, on my server, create a website for the sites under development, using a host header of dev.ClientSite1.com, dev.ClientSite2.com...then, once the site is ready to go live, just change the host header to www.ClientSite1.com, www.ClientSite2.com? Am I understanding the process? This is the process I have been using: On my development PC, everything is viewed through "http://localhost/ClientSite1/index.cfm"; (ClientSite1 being a virtual directory under the default website) On my server, I would set up a virtual directory for the site under the default web site, and tell the client to go to www.MyDefaultWebsite.com/ClientSite1/index.cfm... Then when the site was ready to go live, I would create a new website with host headers of www.ClientSite1.com and ClientSite1.com. I would setup paths in the Application.cfm for assets, etc., based on the CGI.Server_Name. Would the advantage of using the DNS method of managing site development be that I would be able to avoid having CF parse through the Application.cfm each time to determine what paths it should use, therefore saving time and resources in processing? (Not to mention having to figure out all the paths and their variations...) I guess I would still have to setup the Application.cfm to differentiate between localhost (for development) and server setup. I do a lot of development on a laptop and am not always plugged in to the network, so I put MySQL and CF on my laptop for development, too... Rick -----Original Message----- From: Calvin Ward [mailto:[EMAIL PROTECTED] Sent: Monday, February 28, 2005 5:48 AM To: CF-Talk Subject: RE: How to set virtual sites for localhost viewing? Hi Rick, Basically, you'll need to point the DNS entry for each development site to your development server. Let's say that your server IP is 332.278.984.870 (which is impossible), then you would want to point dev.clientsite.com to that IP. (alternatively you can use an alias to whatever site is on that server now that belongs to you, then you only have to use the IP once). On your dev server, you will want to then create a new web site for ClientSite, and in the host header for that site, put dev.clientsite.com. Aside from initial setup for each individual site, you shouldn't have to mess with the DNS except for removing it when the need is no longer there. Consider it part of the process of setting up, unsetting up clients. Calvin -----Original Message----- From: Rick Faircloth [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 23, 2005 3:32 PM To: CF-Talk Subject: RE: How to set virtual sites for localhost viewing? >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) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:196854 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
