Re: [cobalt-users] non-virtual host help NEWBIE <:*)

[Kris Dahl <krislists@xxxxxxxxxxxxx>]

on 4/19/00 5:31 PM, Christian Bonanno at cbonanno@xxxxxxxxx wrote:

>> on 4/19/00 4:28 PM, Christian Bonanno at cbonanno@xxxxxxxxx wrote:
>> 
>>> Cannot understand how to do this:
>>> My website is called chapelhillarts.com. I wish to give people
>>> yourname.chapelhillarts.com addresses for their web pages. I will
>>> have a few sites with their own IP but most will just point to
>>> http://www.chapelhillarts.com/~username/
>>> 
>>> Does anyone have the steps I need to do this?
>>> 
>>> For example; do I have to register that name on internic? I need
>>> silly questions like that answered.
>> 
>> Well essentially, you've got a couple of things you're going to need to do.
>> 
>> Create a record in the DNS for each user.  You should be able to use a A or
>> CNAME record to point to the single IP that will be name-based virtual
>> hosting all this.
> 
> OK. Did this. Created a DNS record for pagedesign.chapelhillarts.com
> -> www.chapelhillarts.com
> 
>> Then you create a virtual host record in apache to snag requests for
>> yourname.chapelhillarts.com and redirect it to /somewhere/on/the/filesystem
>> (which can be /home/sits/home/users/yourname/web, if you want).
>> 
>> This would require hacking the httpd.conf file on your own.
> 
> I have the httpd.conf file --- GREEK ---- Do I add the following?
> 
> #<VirtualHost host.some_domain.com>
> #ServerAdmin webmaster@xxxxxxxxxxxxxxxxxxxx
> #DocumentRoot /www/docs/host.some_domain.com
> #ServerName host.some_domain.com
> #ErrorLog logs/host.some_domain.com-error_log
> #TransferLog logs/host.some_domain.com-access_log
> #</VirtualHost>
> 
>> 
>> I would just take the approach that they are each their own site on the
>> rack.  Setup the DNS and add a new site.  Essentially the cobalt software
>> will set that all up for you.  Should be pretty straightforward.
> 
> <:^(

I would suggest just creating a new site for each accoun (which is what the
Raq was really designed to do).

But yes, you would create a virtualhost in the httpd.conf (use that template
if you'd like).  But this is exactly  what it will do, only there are other
benefits (such as the GUI for administration, etc.).

So I would try to use the interface if you can.

-k