You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

UPGRADING 2.9KB

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