Hi again,
> > What you want to do is specify a a separate <VirtualHost>
> container for each
> > domain and ScriptAlias to the apropriate cgi directory within each
> > container.
> >
> > Remember, you can specify _nearly_ any apache attribute within a
> > <VirtualHost> container.
> >
> > Hope that helps,
> >
> > Sarton
>
> if you do that then the users do not have their own cgi-bin since
> scriptalias
> is going to be used for the regular cgi-bin. Any exemple will be
> appreciated.
I can see why you would think that. The best way to view apache is as if it
only has virtualhosts. A lot of the main server configuration (specifically
the content configuration, not the configuration for the operation of
apache) can be removed or ignored (I am not suggesting you do this however).
When a site is accessed, the environment is set according to the virtualhost
container, including the scipt execution directory. If this wasn't possible,
you would have to run a separate apache per individual website. I'm sure it
was done in the past but it's a bit retro for me ;)
Here's an example of the sort of thing you'd have:
<Directory /path/to/your/domain/cgis>
Options ExecCGI
Allow from All
AllowOverride None AuthConfig
</Directory>
ScriptAlias /webmail "/path/to/your/domain/cgis/"
Sarton
