To check out this repository please hg clone the following URL, or open the URL using EasyMercurial or your preferred Mercurial client.
root / doc / UPGRADING @ 441:cbce1fd3b1b7
History | View | Annotate | Download (1.9 KB)
| 1 | 0:513646585e45 | Chris | == Redmine upgrade |
|---|---|---|---|
| 2 | |||
| 3 | Redmine - project management software |
||
| 4 | 441:cbce1fd3b1b7 | Chris | Copyright (C) 2006-2011 Jean-Philippe Lang |
| 5 | 0:513646585e45 | Chris | 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 | 210:0579821a129a | Chris | 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 | 0:513646585e45 | Chris | |
| 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 | |||
| 23 | 5. Generate a session store secret |
||
| 24 | |||
| 25 | Redmine stores session data in cookies by default, which requires |
||
| 26 | a secret to be generated. Under the new application directory run: |
||
| 27 | rake generate_session_store |
||
| 28 | |||
| 29 | DO NOT REPLACE OR EDIT ANY OTHER FILES. |
||
| 30 | |||
| 31 | 6. Migrate your database |
||
| 32 | |||
| 33 | 441:cbce1fd3b1b7 | Chris | If you are upgrading to Rails 2.3.11 as part of this migration, you |
| 34 | 0:513646585e45 | Chris | need to upgrade the plugin migrations before running the plugin migrations |
| 35 | using: |
||
| 36 | rake db:migrate:upgrade_plugin_migrations RAILS_ENV="production" |
||
| 37 | |||
| 38 | Please make a backup before doing this! Under the new application |
||
| 39 | directory run: |
||
| 40 | rake db:migrate RAILS_ENV="production" |
||
| 41 | |||
| 42 | If you have installed any plugins, you should also run their database |
||
| 43 | migrations using: |
||
| 44 | rake db:migrate_plugins RAILS_ENV="production" |
||
| 45 | |||
| 46 | 7. Clean up |
||
| 47 | |||
| 48 | Clear the cache and the existing sessions by running: |
||
| 49 | rake tmp:cache:clear |
||
| 50 | rake tmp:sessions:clear |
||
| 51 | |||
| 52 | 8. Restart the application server (e.g. mongrel, thin, passenger) |
||
| 53 | |||
| 54 | 9. Finally go to "Administration -> Roles & permissions" to check/set permissions |
||
| 55 | for new features, if any |
||
| 56 | |||
| 57 | == Notes |
||
| 58 | |||
| 59 | 441:cbce1fd3b1b7 | Chris | * Rails 2.3.11 is required for versions 1.2.x. |
| 60 | 0:513646585e45 | Chris | |
| 61 | == References |
||
| 62 | |||
| 63 | * http://www.redmine.org/wiki/redmine/RedmineUpgrade |