Reply within.

* Stephen Boulet <[EMAIL PROTECTED]> wrote:

>
> On Apr 1, 2008, at 3:23 PM, Corey Van Allen wrote:
>> 2. Edit tracks/public/.htaccess as follows
>>     diff .htaccess-new .htaccess-org
>>     3,4c3,4
>>     < AddHandler fcgid-script .fcgi
>>     < #AddHandler fastcgi-script .fcgi
>>     ---
>>> # AddHandler fcgid-script .fcgi
>>> AddHandler fastcgi-script .fcgi
>>     34c34,35
>>     < RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]
>>     ---
>>> RewriteRule ^(.*)$ dispatch.cgi [QSA,L]
>
> Sorry for being diff-impaired. Is this right?
>
> AddHandler fastcgi-script .fcgi
> AddHandler cgi-script .cgi
> Options +FollowSymLinks +ExecCGI

If you are using fastcgi then you should have
AddHandler fastcgi-script .fcgi

if you are using fcgid then you should have
AddHandler fcgid-script .fcgi

> and then
>
> RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]

correct.

> I didn't enable the alias in .htaccess because apache2 complained.
>
> Another issue I'm having is with my alias directive. I have the following 
> in my /etc/apache2/sites-enabled/myown-ssl:
>
> AddHandler fcgid-script .fcgi
> Alias /tracks /var/www/tracks-1.5/public
>
>     ServerName rails
>     DocumentRoot /var/www/tracks-1.5/public
>     ErrorLog /var/www/tracks-1.5/log/apache.log
>
>     <Directory /var/www/tracks-1.5/public/>
>                 Options +FollowSymLinks +ExecCGI
>                 AddHandler fcgid-script .fcgi
>                 AllowOverride all
>                 Allow from all
>                 Order allow,deny
>                 ErrorDocument 500 "<h2>Application error</h2>Rails 
> application failed to start properly"
>                 RewriteEngine On
>                 RewriteRule ^$ index.html [QSA]
>                 RewriteRule ^([^.]+)$ $1.html [QSA]
>                 RewriteCond %{REQUEST_FILENAME} !-f
>                 RewriteRule ^(.*)$ dispatch.cgi [QSA,L]
>                 FCGIWrapper "/usr/bin/ruby 
> /var/www/tracks-1.5/pulic/dispatch.fcgi" .fcgi
>     </Directory>

Your alias should have trailing slashes
Alias /tracks/ /var/www/tracks-1.5/public/
>
> I would assume that most people would want to use an alias if they don't 
> want tracks to take over their entire web server. Did I do the alias 
> incorrectly?

You could do virtual hosting and have it point to say
tracks.example.com while still having www.example.com point to your
default website. Look here for more details on that.
http://httpd.apache.org/docs/2.0/vhosts/name-based.html

-- 
Corey
_______________________________________________
Tracks-discuss mailing list
[email protected]
http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss

Reply via email to