I usually great another domain (like project366.<domain>, ie, pr2346.mrdata.com for my mrdata.com) and then use htaccess file to limit views. This way the base stays the same. Sure, could scan DNS and find it, but the htaccess blocks most there.
Blake Oliviaiam 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 > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
