I am tying to run ROR on apache 2 with suse linux 9.3,
and I do not succeed with it.
I set rubby und rails and all scripts are running fine.
my Document root :
/srv/rails/demo/public
I did not setup FastCGI because I could not run it with
normal CGI jet.
my Virtual Server runs on 192.168.0.111
ServerName rails
DocumentRoot /srv/rails/demo/public
<Directory /srv/rails/demo/public>
Options ExecCGI FollowSymLinks
AllowOverride all
Allow from all
Order allow,deny
I even “chmod 777 /srv/rails/* -R”
whenever I try to connect I get the following answer
in the browser (sorry some of it is german):
Die Anfrage kann nicht beantwortet werden, da im Server >ein interner Fehler aufgetreten ist. Der Server ist >entweder überlastet oder ein Fehler in einem CGI-Skript >ist aufgetreten.
Sofern Sie dies für eine Fehlfunktion des Servers >halten, informieren Sie bitte den Webmaster hierüber.
when I check the apache error log(/var/log/apache2/error_log)
logs I find the following :
[Tue Jan 10 13:20:33 2006] [alert] [client 192.168.0.150]
/srv/rails/demo/public/.htaccess: Invalid command ‘RewriteEngine’,
perhaps mis-spelled or defined by a module not included in the server
configuration
I compared every thing with the rails-wiki for fedora
but I dont find the problem.
[Tue Jan 10 13:20:33 2006] [alert] [client 192.168.0.150]
/srv/rails/demo/public/.htaccess: Invalid command ‘RewriteEngine’,
perhaps mis-spelled or defined by a module not included in the server
configuration
The mod_rewrite module was not loaded at server start. This is normal
for SuSe 9.x and Suse 10 from what I have seen.
Open up the file /etc/sysconfig/apache2 and find the line that starts
with APACHE_MODULES=. At the end of the string add the word
“rewrite” (without quotes) and restart your server with /etc/init.d/
apache2 restart.
On Tue, 2006-01-10 at 10:31 +0100, ramy higazi wrote:
I did not setup FastCGI because I could not run it with
Order allow,deny
Apache/2.0.50 (Linux/SUSE)
[Tue Jan 10 13:20:33 2006] [alert] [client 192.168.0.150]
/srv/rails/demo/public/.htaccess: Invalid command ‘RewriteEngine’,
perhaps mis-spelled or defined by a module not included in the server
configuration
Your installation of apache needs to have mod_rewrite installed and
included. check the IncludeModule area of your apache setup, or suse’s
package management to see if mod_rewrite for apache is installed.