RedmineUpgrade » History » Version 75

Version 74 (Go MAEDA, 2015-03-06 10:11) → Version 75/82 (Toshi MARUYAMA, 2015-04-28 06:08)

h1. Upgrading

The documentation below is based on upgrading to Redmine 2.x and higher. You can view a previous version for upgrading to Redmine 1.x "here":/projects/redmine/wiki/RedmineUpgrade?version=53.


h2. Step 1 - Check requirements

The first step to upgrading Redmine is to check that you meet the [[RedmineInstall#Requirements|requirements]] for the version you're about to install.

h2. Step 2 - Backup

It is recommended that you backup your database and file uploads. Most upgrades are safe but it never hurts to have a backup just in case.

h3. Backing up the files

All file uploads are stored to the @files/@ directory. You can copy the contents of this directory to another location to easily back it up.

h3. MySQL database

The @mysqldump@ command can be used to backup the contents of your MySQL database to a text file. For example:
/usr/bin/mysqldump -u <username> -p<password> <redmine_database> | gzip > /path/to/backup/db/redmine_`date +%y_%m_%d`.gz

h3. SQLite database

SQLite databases are all contained in a single file, so you can back them up by copying the file to another location.

h3. PostgreSQL

The @pg_dump@ command can be used to backup the contents of a PostgreSQL database to a text file. Here is an example:
/usr/bin/pg_dump -U <username> -Fc --file=redmine.sqlc <redmine_database>

h2. Step 3 - Perform the upgrade

Now it's time to perform the actual upgrade. This process is different depending on how you downloaded Redmine. You only need to perform *one* of the following options.

h3. Option 1 - Download a stable release

1. [[Download]] the release in either tar.gz or zip format and uncompress the new program archive in a new directory.

Make sure the newly extracted and copied files and directories have the correct owner and group set, so that the user/group running your application server can actually access the files.
Also, remember to add write permissions to the @files@, @log@ and @tmp@ directory.

2. Copy your database settings-file @config/database.yml@ into the new @config@ directory. If you're running Redmine >= 1.4 with mysql and ruby1.9, change the database adapter to `mysql2`.

3a. Copy your base configuration settings-file @config/configuration.yml@ into the new @config@ directory.

3b. Or, *if upgrading from version older than 1.2.0*, copy your email settings from your @config/email.yml@ into the new @config/configuration.yml@ file that can be created by copying the available @configuration.yml.example@ file.

4. Copy the @files@ directory content into your new installation (this directory contains all your uploaded files).

5. Copy the folders of your *custom* plugins from your @plugins@ directory (or @vendor/plugins@ directory if upgrading from a 1.x version) into new installation @plugins@ directory. Make sure that you copy only plugins that are were not initially bundled with your previous Redmine setup.

6. Install the required gems by running:

bundle install --without development test

If ImageMagick is not installed on your system, you should skip the installation of the rmagick gem using:

bundle install --without development test rmagick

Only the gems that are needed by the adapters you've specified in your database configuration file are actually installed (eg. if your config/database.yml uses the 'mysql2' adapter, then only the mysql2 gem will be installed). Don't forget to re-run `bundle install` when you change config/database.yml for using other database adapters.

If you need to load some gems that are not required by Redmine core (eg. fcgi), you can create a file named Gemfile.local at the root of your redmine directory. It will be loaded automatically when running `bundle install`.

7. Run the following command from your new Redmine root directory:

If you're upgrading from Redmine 2.x or below, remove the following file if it exists:
* config/initializers/secret_token.rb

Then generate a new secret by running the following command under the application directory:

bundle exec rake generate_secret_token

Alternatively, you can store this This will generate a file (@config/initializers/secret_token.rb@) with a random secret in config/secrets.yml:
used to secure session data.

8. Check for any themes that you may have installed in the @public/themes@ directory. You can copy them over but checking for updated version is ideal.

VERY IMPORTANT: do NOT overwrite @config/settings.yml@ with the old one.

h3. Option 2 - Upgrading from a SVN checkout

1. Go to the Redmine root directory and run the following command:
svn update

2. Install the required gems by running the following command:

bundle update

h2. Step 4 - Update the database

This step is the one that could change the contents of your database. Go to your new redmine directory, then migrate your database:

bundle exec rake db:migrate RAILS_ENV=production

If you have installed any plugins, you should also run their database migrations:

bundle exec rake redmine:plugins:migrate RAILS_ENV=production

h2. Step 5 - Clean up

1. Clear the cache and the existing sessions:

bundle exec rake tmp:cache:clear tmp:sessions:clear RAILS_ENV=production

2. Restart the application server (e.g. puma, thin, passenger)

3. Finally go to _"Admin -> Roles & permissions"_ to check/set permissions for the new features, if any.

h2. Common issues

h3. Errors with repository management

There were several new features added to the reposman.rb file, make sure you have a group specified if you're having issues ( --group=groupnamehere). Also, make sure you follow the instructions [[Repositories_access_control_with_apache_mod_dav_svn_and_mod_perl|here]] again if you only copied your, and update your Apache configuration as the recommended configuration has changed.

h3. Generating a new @secret_token.rb@

Before version:2.0.0, a @session_store.rb@ file needed to be generated in Redmine's @config@ directory for the cookie based sessions to work.

Starting from version:2.0.0, the @session_store.rb@ file should not exist. Instead, the following command will generate the @secret_token.rb@ file:

bundle exec rake generate_secret_token

_Note: The code repository for Redmine does not contain the config/initializers/secret_token.rb file, it is created by the above rake command._

h3. Related Resources

These resources may help you with your Redmine upgrade:

* Error while browsing the wiki history after upgrading from Redmine 1.x with SQLite: see #12501
* "mod_fcgid for Apache2": helped us get Rails running on Apache 2
* "Running Redmine on Apache":
* "Notes about our 0.8.6 to 0.9.3 upgrade issues and how to resolve them": --cybersprocket (2010-04-25)
* "Notes about our 0.9.6 to 1.0(RC) upgrade process": --cybersprocket (2010-08-14)