Re: [cobalt-users] Previewing a name-based virtual site

[Kevin Murphy <kevin@xxxxxxxxxxxxx>]

Tony:

> preview their new site. When we were on the Sun platform we used to create a
> cname like  newclientname.ourname.com with a symlink to their htdoc
> directory until the new dns propogated.

This is what I'm trying to do!  But it seems that, on the RaQ, it's
almost impossible.  I tried the cname/symlink scenario, but it didn't
work - the RaQ wouldn't resolve the symlink properly, and climbing back
up the directory tree to get to the site isn't possible, either.

The more I think about it, since my other scenario worked to add our IP
address as a VirtualHost, then I should be able to go into the
httpd.conf file and change an individual site's ServerName line to
theirsite.ourraq.com.  This is okay, but it still means going to the
server to change a site from 'preview' to 'live'.

WAIT!  I think I've got it....

When we set up the site initially, we should set them up in the Cobalt
interface as 'theirsite.ourraq.com'.  Then, they can access the site
there all they want, as long as we put them in our dns table - extra
work, but not a big deal.  When the domain propagates, we use the Cobalt
interface to change them to www.theirdomain.com, and they're all set.
Cobalt takes care of re-writing httpd.conf, and restarting the server
and all that fun stuff.

Anybody got any thoughts?  Sounds like it'll work, right?  Yep.  Just
tried it.  Works like a charm.  Only trouble is, we can't set up email
accounts until the website is 'live', and if we transfer the domain
before we get the site running, we've got an issue there.  It's always something.

I just wish there was a way we could do it without having to change
things around all the time - seems like extra work.

Thanks.

-Kevin


> 
> -----Original Message-----
> From: cobalt-users-admin@xxxxxxxxxxxxxxx
> [mailto:cobalt-users-admin@xxxxxxxxxxxxxxx]On Behalf Of Will DeHaan
> Sent: Tuesday, February 08, 2000 2:01 PM
> To: cobalt-users@xxxxxxxxxxxxxxx
> Subject: Re: [cobalt-users] Previewing a name-based virtual site
> 
> The best way to test a name-based web site before your DNS domain
> registrations are complete is to take control of your own DNS service.
> Every RaQ and Qube out there has a DNS server built-in.  Simply add a
> forward (A) record in your DNS from your
> www.namebasedbutnotyetregistered.com to the IP address used by that
> site.  Save Changes.  Set the RaQ to your primary DNS server on your
> local PC.  Now pull up that site on your web browser, test away.
> 
> The public can never access a name-based site without correctly
> configured public DNS service.  Register those domains if you haven't
> already.  www.123domains.com is running a sale, $28 for two years
> service.
> 
>         -- Will
> 
> Kevin Murphy wrote:
> >
> > Hello.
> >
> > We have been using a Coblat RaQ2 for quite some time for a single
> > client, and are beginning now to host multiple sites on it.  We are
> > planning to use name-based hosting to accomplish this.
> >
> > My question is deceptively simple.  When a virtual site is added to the
> > primary IP address on the server, how do I access that site in order to
> > test it?
> >
> > Currently, we "stage" all our sites as users in the home directory.
> > This allows us to send clients to 'our.cobalt.server/users/theirsite',
> > and works well.  But I don't want to be forced to move their sites when
> > they go "live" because of the limits of this server.  There's got to be
> > a better way!
> >
> > >From what I can tell, the directory structure of the server prevents you
> > from accessing a new  site directly by IP, as the IP-based hosting
> > points at a specific web directory, and not the "root" of all web
> directories.
> >
> > I have tried adding a symlink to the directory created by the new domain
> > in /home/sites/home/users, but I always get "file not found" when I try
> > to access it in the browser.
> >
> > I also tried adding a second entry in the ServerAlias line in
> > httpd.conf, and that didn't seem to work, either - it just redirected
> > the site over to the existing domain!  Not useful for my purposes.
> >
> > So, I'm stuck.
> >
> > Do I need to change the DocumentRoot for the IP I'm going to host all
> > the sites under so it  points at a higer level directory, and then put
> > in a new ServerName line for the existing machine on that IP?  But won't
> > that screw up the Cobalt Interface?  Or is httpd.conf written
> > separately, and only re-written when it's asked to?
> >
> > Any hints are greatly appreciated.  I'm sure I'm not the first person to
> > encounter this problem.
> >
> > Thanks!
> >
> > -Kevin
> >
> > --
> > Kevin Murphy
> > Director of Technology
> >
> > Glen Group
> > Marketing and Advertising Design
> > P.O. Box 2838, 170 Kearsarge Street
> > North Conway, New Hampshire 03860
> > http://www.glengroup.com
> >
> > Voice: 603-356-3030 * FAX: 603-356-3991
> >
> > _______________________________________________
> > cobalt-users mailing list
> > cobalt-users@xxxxxxxxxxxxxxx
> > http://list.cobalt.com/mailman/listinfo/cobalt-users
> 
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> http://list.cobalt.com/mailman/listinfo/cobalt-users
> 
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> http://list.cobalt.com/mailman/listinfo/cobalt-users

-- 
Kevin Murphy
Director of Technology

Glen Group
Marketing and Advertising Design
P.O. Box 2838, 170 Kearsarge Street
North Conway, New Hampshire 03860
http://www.glengroup.com

Voice: 603-356-3030 ? FAX: 603-356-3991