If you are using something like codeigniter (http://codeigniter.com) this is
done easily. There is a config in which you define the root/site url. But of
course you could hand roll your own as well.

On Wed, Aug 26, 2009 at 10:51 AM, Trevor Rosen <[email protected]>wrote:

>
> Make all your links relative to the root. And then change what the
> root is.
>
> How do you do that? Apache config -- especially vhosts (virtual hosts)
>
> You'll want to mess with these two directives as appropriate:
>
> - DocumentRoot: A virtual host will let you set up
> "staging.foocompany.com" to point to wherever folder on the server you
> want via the DocumentRoot directive -- the DocumentRoot's job is to
> say where on the machine your site's code lives.
>
> - ServerName: says what the server name is (what you'd put in the URL
> bar of a browser to get there)
>
> For go-live, you could change either of these in the appropriate vhost
> block to go from staging to live (assuming the DNS already points to
> that server).  After that, just restart Apache and you're done.
>
> You might be on shared hosting.  If so, you can usually find a GUI-
> based option to manipulate this stuff.  And the DNS stuff should
> already be handled for you, since you're making subs of an existing
> domain.  You can easily learn more about Apache if you have a Mac --
> it powers web serving in OS X.
>
> best of luck,
>
> -TR
>
> On Aug 26, 2009, at 10:33 AM, 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
> >
> >
> > >
>
> ServerName: says what the server name is (what you'd put in the URL
> bar of a browser to get there)
>
> For go-live, you could change either of these in the appropriate vhost
> block to go from staging to live (assuming the DNS already points to
> that server).
>
> On shared hosting situations, you can usually find a GUI-based option
> to manipulate this stuff.  And the DNS stuff should already be handled
> for you, since you're making subs of an existing domain.
>
> On OS X,
>
> best of luck,
>
> -TR
>
> Make all your links relative to the root,
> On Aug 26, 2009, at 10:33 AM, 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
> -~----------~----~----~----~------~----~------~--~---
>
>


-- 
Keith Aric Hall

http://www.keitharichall.com/
twitter: keitharichall

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to