We tried to setup a rails application in a server subfolder in a way that could have been accessible through an URL like http://servername/rails, so we followed the configuration manual for mod_rails.We found that, to make rails works in a subfolder, should have used the Apache parameter RailsBaseURI.
With a great surprise, that didn’t worked so we started trying all possible apache configuration combinations to avoid that 404 error that was becoming a nightmare.
After few hours we started doubting about our Apache knowledge and even about our capacity of reading and following a couple of stupid instructions on a website!
We gave up and we started googling around when… the solution came out from dozens of blogs, forums and newsletters:
MOD_RAILS IS NOT COMPATIBLE WITH RAILS 2.2.2 AND ITS NEW ROUTING SYSTEM
“HOLY CRAP” was our esclamation and I will not mention here all the italian’s bad words that suddenly came out from our mounth!
So, here the solution: put this line here
config.action_controller.relative_url_root = "/guestbook"
in your environment.rb
Now restart apache and enjoy!
ps. why hadn’t we changed mod_rails with mongrel or anything different? I don’t know!!!!
I’m doing the same thing, but it does not work for me
.
Comment by Marcello Nuccio — March 31, 2009 @ 6:18 pm
I have found the problem!
You cannot use PassengerHighPerformance on.
Leave it at the default “off” and it works.
Comment by Marcello Nuccio — March 31, 2009 @ 6:23 pm