Note that there are some explanatory texts on larger screens.

plurals
  1. POPhusion Passenger Configuration via .htaccess
    primarykey
    data
    text
    <p>I'm trying to install Redmine, and I am having trouble making Phusion Passenger work with any directories other than the DocumentRoot.</p> <p>I've put the public directory downloaded from Redmine into ~/www/public/entry/redmine.mysite.com/, and the rest of the directories in ~/www/app/redmine.mysite.com/.</p> <p>I've added the following line to the .htaccess file inside the public folder: </p> <pre><code>PassengerAppRoot ~/www/app/redmine.mysite.com </code></pre> <p>Whenever I try to load up the page, it just gives me the plain Mozilla file not found page.</p> <p>Any thoughts?</p> <hr> <p>Additional Info:</p> <p>I have a codebase set up so that apache resolves any given request URI to a particular entry folder, as follows:</p> <p>DocumentRoot is ~/www/public</p> <p>In this folder is a .htaccess file, including the following rule:</p> <pre><code>RewriteCond ${lowercase:%{SERVER_NAME}} ^(dev\.)?(stg\.)?(www\.)?(.*)$ RewriteCond %{REQUEST_URI} !^/resource/(.*)$ RewriteRule !^entry/ entry/%4%{REQUEST_URI} </code></pre> <hr> <p>If I create a new VirtualHost for port 3000, with DocumentRoot=~/www/public/entry/redmine.mysite.com/, everything loads up correctly.</p> <p>However, if instead I use my codebase's mod_rewrite-based resolution, I get a page not found error.</p> <hr> <p>If I visit redmine.mysite.com/404.html, it loads the 404.html page that is in the correct folder.</p> <hr> <p>If I change the PassengerAppRoot to ~/www/app/redmine.mysite.com/test, it informs me that the directory does not appear to be a valid Ruby on Rails application root.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload