You could do this a number of ways. Probably the best would be like Butta' suggested, setup a local test environment on your machine (or anywhere on a network with an IP, actually) and alter your system's HOSTS file (/etc/hosts on unix/mac, or c:\windows\system32\drivers\etc\hosts on windows) to point to that IP for the domain you're using. Then you can test your website using the same domain as the production/live site, but aren't actually touching that site at all.
For example, if you setup a local webserver on your machine @ 127.0.0.1 (localhost) to do the new site development, you would put this in your HOSTS file www.yourdomain.com 127.0.0.1 Then, when you make a request for www.yourdomain.com from *your computer only*, it serves it from the local webserver, and not from the live site - and the live site remains intact for everyone else on the interweb. If there is a development server already on your network, you can configure that server to house the files for the site you're developing, then substitute 127.0.0.1 with the IP of that webserver in your HOSTS file. And if you need others on your network to access the test site, you can either make a *temporary, local* DNS change on your network to point your domain to the development IP, or have the people that need to see it make the same HOSTS file change as you. Won't work with 127.0.0.1, of course, but if your machine has a real network address, they can plug that in - as long as that's the interface your webserver is running on. Hope that helps! -michael On Wed, Aug 26, 2009 at 10:32 AM, Butter<[email protected]> wrote: > you can create a protected directory or a private subdomain through hosting, > but some hosting won't let you do that unless you upgrade. So you could > also setup a test environment on your computer for development purpose. > > On Wed, Aug 26, 2009 at 9:33 AM, Oliviaiam <[email protected]> > wrote: >> >> Does anyone have an answer to this probably simplistic question?... >> How do you create a site so that it's non-public facing while you >> develop it and then easily converted to the correct domain? By that, >> I mean converting from the non-public URL to the public one without >> having to change every single internal link? ---Thanks >> >> >> > > > > > -- michael --~--~---------~--~----~------------~-------~--~----~ Our Web site: http://www.RefreshAustin.org/ You received this message because you are subscribed to the Google Groups "Refresh Austin" group. [ Posting ] To post to this group, send email to [email protected] Job-related postings should follow http://tr.im/refreshaustinjobspolicy We do not accept job posts from recruiters. [ Unsubscribe ] To unsubscribe from this group, send email to [email protected] [ More Info ] For more options, visit this group at http://groups.google.com/group/Refresh-Austin -~----------~----~----~----~------~----~------~--~---
