Work:Default Rails htaccess
From Zoelife4U Wiki
Rails applications yet no .htaccess
Well it seems that when running the command to create a Rails application, it no longer creates that much needed .htaccess file in the public/ directory, and you'll notice alot of people pissed off about this, so below is a default Rails .htaccess file set to use FastCGI.
# General Apache options AddHandler fcgid-script .fcgi AddHandler cgi-script .cgi Options +FollowSymLinks +ExecCGI # If you don't want Rails to look in certain directories, # use the following rewrite rules so that Apache won't rewrite certain requests # # Example: # RewriteCond %{REQUEST_URI} ^/notrails.* # RewriteRule .* - [L] # Redirect all requests not available on the filesystem to Rails # By default the cgi dispatcher is used which is very slow # # For better performance replace the dispatcher with the fastcgi one # # Example: # RewriteRule ^(.*)$ dispatch.fcgi [QSA,L] RewriteEngine On # If your Rails application is accessed via an Alias directive, # then you MUST also set the RewriteBase in this htaccess file. # # Example: # Alias /myrailsapp /path/to/myrailsapp/public # RewriteBase /myrailsapp RewriteBase / RewriteRule ^$ index.html [QSA] RewriteRule ^([^.]+)$ $1.html [QSA] RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ dispatch.fcgi [QSA,L] # In case Rails experiences terminal errors # Instead of displaying this message you can supply a file here which will be rendered instead # # Example: # ErrorDocument 500 /500.html ErrorDocument 500 "<h2>Application error</h2>Rails application failed to start properly"
And for those missing Gems, add the following to ~/.bashrc at the bottom:
export PATH=$PATH:$HOME/packages/bin:$HOME/.gems/bin export GEM_HOME=$HOME/ruby/gems export GEM_PATH=$GEM_HOME:/usr/lib64/ruby/gems/1.8 export GEM_CACHE=$GEM_HOME/cache export PATH=$PATH:$HOME/ruby/gems/bin
