|
If you were logged in you would be able to see more operations.
|
|
|
|
File Attachments:
|
1.
localhost.2011-11-15.log (15 kB) 15/Nov/11 07:52 PM - mhuffnagle
|
|
Environment:
|
JRuby 1.6.5 under RVM, Tomcat 7.0.22, rails 3.0.10, reproduced on both Centos 5.5 and OS X 10.6.8, warbler 1.3.2
JRuby 1.6.5 under RVM, Tomcat 7.0.22, rails 3.0.10, reproduced on both Centos 5.5 and OS X 10.6.8, warbler 1.3.2
|
|
Warbler version: 1.3.2
When I deploy the war generated by Warbler to Tomcat, it's failing because it is trying to set config.action_controller.relative_url_root. That setting has been replaced by the environment variable RAILS_RELATIVE_URL_ROOT.
There is a StackOverflow posting which talks about the change here: http://stackoverflow.com/questions/5558900/changing-the-base-url-for-rails-3-development
I've found that the app works when I deploy it to root, but always fails when I deploy it to a some sub-url.
|
|
Description
|
Warbler version: 1.3.2
When I deploy the war generated by Warbler to Tomcat, it's failing because it is trying to set config.action_controller.relative_url_root. That setting has been replaced by the environment variable RAILS_RELATIVE_URL_ROOT.
There is a StackOverflow posting which talks about the change here: http://stackoverflow.com/questions/5558900/changing-the-base-url-for-rails-3-development
I've found that the app works when I deploy it to root, but always fails when I deploy it to a some sub-url. |
Show » |
Sort Order:
|
Bug
Open
Major
Warbler-generated war file fails to load in Tomcat using relative_url_root
It looks like this was related to https://github.com/rails/rails/pull/3646