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