Apache Phusion Passenger 3 RackBaseURI only works in a production environment for Rails 3

Question

I have several rails of 3 applications that work under their own Rails / Rack BaseURI.

In Passenger 2, I used RailsBaseURI to "mount" individual rails applications in the same domain; it worked fine. I upgraded to Passenger 3.0.2, and now that I am in development mode, my Rails 3 applications want to add and add baseURI, but only in the development environment. Everything is good in production.

For instance:

The application lives in / fsroot / otherdir / myapp The target file lives in /fsroot/otherdir/myapp/public/path/to/asset.css

in vhost configuration: RackBaseURI / myapp

Note: the symbolic link in virtualhost DocumentRoot is called myapp and is pointed to / fsroot / otherdir / myapp / public

In view: stylesheet_link_tag '/path/to/asset.css'

will create

No such file or directory - Asset file not found in '/fsroot/otherdir/myapp/public/myapp/path/to/asset.css'

Note that RackBaseURI shows here before and after the shared folder.

I tried copying the development.rb environment file to production.rb and reloading apache, but it does the same. Apparently, there is some other directive that is adopted in each of these environments, but I have no idea what it will be. I tried using RailsBaseURI and RackBaseURI, but both were the same.

Rail Management 3 Wizard is welcome.

Answer 1

So far I'm not sure this may help:

RailsBaseURI RackBaseURI, Rails 3 Passenger 3

: http://wiki.railsplayground.com/railsplayground/show/How+To+use+Phusion+Passenger