HowTo Install Redmine in a sub-URI » History » Revision 17
Revision 16 (Evgeniy Dushistov, 2016-06-26 12:50) → Revision 17/18 (Cyril Jouve, 2018-03-08 22:24)
{{toc}}
h1. HowTo Install Redmine in a sub-URI
This page explains how to run Redmine in a subdirectory of your site, for instance @http://www.mysite.com/redmine/@ ; in such a case, you can feel lost because the classic Redmine install does not work directly, and the links to css or javascript files seem to be broken. In this page, we assume you want to run Redmine under "/redmine/" subdirectory of your site.
h2. Working variant (Sun Jun 26 13:48:50 MSK 2016)
Change the following lines at the bottom of your config/environment.rb
<pre><code lang="ruby">
# Initialize the Rails application
Rails.application.initialize!
</code></pre>
to
<pre><code lang="ruby">
RedmineApp::Application.routes.default_scope = "/redmine"
# Initialize the Rails application
Rails.application.initialize!
</code></pre>
h2. Using Redmine::Utils (preferred solution)
Add the following line at the bottom of your config/environment.rb
<pre>
Redmine::Utils::relative_url_root = "/redmine"
</pre>
Then restart your application.
h2. Using Rails features
Add the following line at the end of your config/environment.rb :
<pre>
ActionController::AbstractRequest.relative_url_root = "/redmine"
</pre>Rails will then prefix all links with "/redmine". It can be considered as the simplest, cleanest and most flexible solution. Then restart your application. In more recent versions of Rails the class hierarchy has changed slightly and you will need to use
<pre>
ActionController::Base.relative_url_root = "/redmine"
</pre>for the class name.
h2. Using Mongrel features
If you run Redmine under Mongrel server, you can alternatively use the "--prefix" option of Mongrel :
<pre>
mongrel_rails start --prefix=/redmine
</pre>
_*Mongrel_rails service "--prefix" directive does NOT work with Rails 2.3.x*
To fix this issue create a file config/initializers/patch_for_mongrel.rb [name of file can be anything]:_
<pre>
# Fix for mongrel which still doesn't know about Rails 2.2's changes,
# We provide a backwards compatible wrapper around the new
# ActionController::base.relative_url_root,
# so it can still be called off of the actually non-existing
# AbstractRequest class.
module ActionController
class AbstractRequest < ActionController::Request
def self.relative_url_root=(path)
ActionController::Base.relative_url_root=(path)
end
def self.relative_url_root
ActionController::Base.relative_url_root
end
end
end
#
# Thanks to http://www.ruby-forum.com/topic/190287
</pre>
You may not run Mongrel on port 80 : if you have an Apache server on the same host, and you run Mongrel on port 8000, you can use the following Apache config to redirect (with Apache's mod_proxy enabled) :
<pre>
ProxyPass /redmine http://localhost:8000/redmine
ProxyPassReverse /redmine http://localhost:8000/redmine
</pre>
h2. Using Passenger (aka mod_rails) features
If you run Redmine under Apache web server with Phusion Passenger module, you can follow "this guide":http://www.modrails.com/documentation/Users%20guide%20Apache.html#deploying_rails_to_sub_uri ; please note it won't work correctly on some versions of Passenger or some Linux distributions.
h2. Using Passenger+Nginx features
See "official guide":http://modrails.com/documentation/Users%20guide%20Nginx.html#deploying_rails_to_sub_uri (This is the only solution that worked for me - 30 Oct 2012)
h2. Using Unicorn+Nginx
nginx config:
<pre>
location /redmine {
alias <PATH_TO>/redmine/public;
try_files $uri/index.html $uri.html $uri @app;
}
</pre>
config/routes.rb
<pre>
Redmine::Utils::relative_url_root = "/redmine"
RedmineApp::Application.routes.draw do
scope Redmine::Utils::relative_url_root do
root :to => 'welcome#index', :as => 'home'
.....
end
end
</pre>
h2. With a reverse proxy
If you have an Apache webserver in front of it (with mod_proxy enabled), or an Apache reverse proxy on another machine, you can run Redmine on a specific port and use this kind of config so it appears to be running in a subdirectory :
<pre>
ProxyPass /redmine http://real-redmine-server.localdomain:3000/
ProxyPassReverse /redmine http://real-redmine-server.localdomain:3000/
</pre>See Apache official documentation to adapt it.
h2. With puma
# Define "RAILS_RELATIVE_URL_ROOT environment variable":http://guides.rubyonrails.org/configuring.html#deploy-to-a-subdirectory-relative-url-root :
<pre><code class="bash>
export RAILS_RELATIVE_URL_ROOT=/redmine
</code></pre> or use [[HowTo_Install_Redmine_in_a_sub-URI#Using-RedmineUtils-preferred-solution|RedmineUtils method]]
This allows rails to generate urls prefixed by RAILS_RELATIVE_URL_ROOT.
# Then update you config.ru:
<pre><code class="ruby">
# This file is used by Rack-based servers to start the application.
require ::File.expand_path('../config/environment', __FILE__)
map ENV['RAILS_RELATIVE_URL_ROOT'] || '/' do
run RedmineApp::Application
end
</code></pre> This allows rack to handle urls prefixed with RAILS_RELATIVE_URL_ROOT.
Both points are necessary.
h2. Old versions of Redmine and Rails
If you run a very old version of Redmine (don't know exactly which ones), maybe your version of Rails' ActionController does not support the "relative_url_root" mentionned above. Then you can look at "this page":https://www.riscosopen.org/wiki/documentation/pages/Running+Rails+applications+from+subdirectories/versions/16 to reproduce the same behaviour, but it is NOT a very good idea in most cases, you should consider upgrading Redmine.
h2. References
If this page did not answered your problems, you can see #2508 or "this thread":http://www.redmine.org/boards/2/topics/2244.
Windows : Configuring Ruby On Rails App in a subdirectory under Apache - http://stackoverflow.com/a/470973/663172
Configuring ruby on rails Action Controller - http://edgeguides.rubyonrails.org/configuring.html#configuring-action-controller