|
1
|
== Redmine upgrade
|
|
2
|
|
|
3
|
Redmine - project management software
|
|
4
|
Copyright (C) 2006-2015 Jean-Philippe Lang
|
|
5
|
http://www.redmine.org/
|
|
6
|
|
|
7
|
|
|
8
|
== Upgrading
|
|
9
|
|
|
10
|
1. Uncompress the program archive in a new directory
|
|
11
|
|
|
12
|
2. Copy your database settings (RAILS_ROOT/config/database.yml)
|
|
13
|
and your configuration file (RAILS_ROOT/config/configuration.yml)
|
|
14
|
into the new config directory
|
|
15
|
Note: before Redmine 1.2, SMTP configuration was stored in
|
|
16
|
config/email.yml. It should now be stored in config/configuration.yml.
|
|
17
|
|
|
18
|
3. Copy the RAILS_ROOT/files directory content into your new installation
|
|
19
|
This directory contains all the attached files.
|
|
20
|
|
|
21
|
4. Copy the folders of the installed plugins and themes into new installation
|
|
22
|
Plugins must be stored in the [redmine_root]/plugins directory
|
|
23
|
Themes must be stored in the [redmine_root]/public/themes directory
|
|
24
|
|
|
25
|
WARNING: plugins from your previous Redmine version may not be compatible
|
|
26
|
with the Redmine version you're upgrading to.
|
|
27
|
|
|
28
|
5. Install the required gems by running:
|
|
29
|
bundle install --without development test
|
|
30
|
|
|
31
|
If ImageMagick is not installed on your system, you should skip the installation
|
|
32
|
of the rmagick gem using:
|
|
33
|
bundle install --without development test rmagick
|
|
34
|
|
|
35
|
Only the gems that are needed by the adapters you've specified in your database
|
|
36
|
configuration file are actually installed (eg. if your config/database.yml
|
|
37
|
uses the 'mysql2' adapter, then only the mysql2 gem will be installed). Don't
|
|
38
|
forget to re-run `bundle install` when you change config/database.yml for using
|
|
39
|
other database adapters.
|
|
40
|
|
|
41
|
If you need to load some gems that are not required by Redmine core (eg. fcgi),
|
|
42
|
you can create a file named Gemfile.local at the root of your redmine directory.
|
|
43
|
It will be loaded automatically when running `bundle install`.
|
|
44
|
|
|
45
|
6. Generate a session store secret
|
|
46
|
|
|
47
|
If you're upgrading from Redmine 2.x or below, remove the following file
|
|
48
|
if it exists: config/initializers/secret_token.rb
|
|
49
|
|
|
50
|
Then generate a new secret by running the following command under the
|
|
51
|
application directory:
|
|
52
|
bundle exec rake generate_secret_token
|
|
53
|
|
|
54
|
Alternatively, you can store this secret in config/secrets.yml:
|
|
55
|
http://guides.rubyonrails.org/upgrading_ruby_on_rails.html#config-secrets-yml
|
|
56
|
|
|
57
|
DO NOT REPLACE OR EDIT ANY OTHER FILES.
|
|
58
|
|
|
59
|
7. Migrate your database
|
|
60
|
|
|
61
|
If you are upgrading to Rails 2.3.14 as part of this migration, you
|
|
62
|
need to upgrade the plugin migrations before running the plugin migrations
|
|
63
|
using:
|
|
64
|
bundle exec rake db:migrate:upgrade_plugin_migrations RAILS_ENV="production"
|
|
65
|
|
|
66
|
Please make a backup before doing this! Under the new application
|
|
67
|
directory run:
|
|
68
|
bundle exec rake db:migrate RAILS_ENV="production"
|
|
69
|
|
|
70
|
If you have installed any plugins, you should also run their database
|
|
71
|
migrations using:
|
|
72
|
bundle exec rake db:migrate_plugins RAILS_ENV="production"
|
|
73
|
|
|
74
|
8. Clear the cache and the existing sessions by running:
|
|
75
|
bundle exec rake tmp:cache:clear tmp:sessions:clear
|
|
76
|
|
|
77
|
9. Restart the application server (e.g. mongrel, thin, passenger)
|
|
78
|
|
|
79
|
10. Finally go to "Administration -> Roles & permissions" to check/set permissions
|
|
80
|
for new features, if any
|
|
81
|
|
|
82
|
== References
|
|
83
|
|
|
84
|
* http://www.redmine.org/wiki/redmine/RedmineUpgrade
|