Re[2]: [cgiwrap-users] real hosting and cgiwrap

[Daniel L. <da...@lo...>]

Hi,

> Since I'm talking about mass-hosting, you probably know, that it's 
> impossible to set several hunderts of ScriptAlias and mod_rewrite rules.

why should this be impossible? I'm doing myself mass-hosting pretty well
with a combined cgiwrap and php-cgiwrap.

You could create templates for your virtualhosts:

  <VirtualHost *>
    ServerAdmin webmaster@%%domain%%
    ServerName %%domain%%
    ServerAlias *.%%domain%%

    [..]
  </VirtualHost>

Which would then be written into a single httpd.conf. Also a
placeholder for %%user%% would make the implementation of cgiwrap
terribly easy, wouldn't it?

Use your imagination. This ain't magic - some lines in
Perl/PHP/Python/Ruby do the trick.

> In addition, scripts shall not only be executable in /cgi-bin/, but 
> everything. The script just should end with .pl or .php.

This is not cgiwrap-related. Please read the manual carefully.

  Options +ExecCGI
  http://httpd.apache.org/docs/mod/core.html#options

> This is done with "AddHandler", not ScriptAlias.

ScriptAlias to make cgiwrap available, AddHandler to add handlers for
file extensions to the wrapper. Looks like this:

  ScriptAlias /cgi-bin/cgiwrap/ /usr/local/cgi-bin/cgiwrap/

  AddHandler phpwrap .php3
  AddHandler phpwrap .php
  AddHandler cgiwrap .cgi
  AddHandler cgiwrap .pl

  Action phpwrap /cgi-bin/cgiwrap/php-cgiwrap/username
  Action cgiwrap /cgi-bin/cgiwrap/cgiwrap/username

I still don't understand your problem. If there WOULD be another
perfect solution, why don't you just use it and stop ranting?
  
-daniel