RedmineUpgrade » History » Version 14

« Previous - Version 14/82 (diff) - Next » - Current version
Eric Davis, 2009-02-26 19:29
Added comment about upgrading plugin migration versions


Upgrading

Before upgrading, check that you meet the requirements for the version you're about to install.

Upgrading from a SVN checkout

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

svn update

2. Migrate your database (please, make a database backup before doing this):

rake db:migrate RAILS_ENV="production" 

3. If you are upgrading from Redmine 0.8.x or trunk < r2493 to Redmine trunk => r2494, you must generate a secret for cookie store:

rake config/initializers/session_store.rb

Also remember that Redmine trunk => r2494 now uses Rails 2.2.2, don't forget to upgrade the existing installation:

gem install rails -v=2.2.2

Also as part of the Rails 2.2.2 upgrade, plugin migrations will need to be updated as well

rake db:migrate:upgrade_plugin_migrations RAILS_ENV="production" 

4. Clear the cache and the existing sessions:

rake tmp:cache:clear
rake tmp:sessions:clear

5. Restart the application and go to "Admin -> Roles & permissions" to check/set permissions for the new features, if any.

Upgrading from a downloaded release

1. Uncompress the new program archive in a new directory.

2. Copy your database settings-file config/database.yml into the new config directory.

3. Copy the email settings-file config/email.yml.example to config/email.yml and edit this file to adjust your SMTP settings.

4. Go to your new redmine directory, then migrate your database (please, make a database backup before doing this):

rake db:migrate RAILS_ENV="production" 

5. If you are upgrading from Redmine 0.8.x or trunk < r2493 to Redmine trunk => r2494, you must generate a secret for cookie store:

rake config/initializers/session_store.rb

Also remember that Redmine trunk => r2494 now uses Rails 2.2.2, don't forget to upgrade the existing installation:

gem install rails -v=2.2.2

6. Copy the RAILS_ROOT/files directory content into your new installation.

7. Restart the application and go to "Admin -> Roles & permissions" to check/set permissions for the new features, if any.