comparison .svn/pristine/94/94b0a87688b1d61b6fb66241d11ae9e0ee65fa3e.svn-base @ 1298:4f746d8966dd redmine_2.3_integration

Merge from redmine-2.3 branch to create new branch redmine-2.3-integration

+== Redmine upgrade
+
+Redmine - project management software
+Copyright (C) 2006-2013  Jean-Philippe Lang
+http://www.redmine.org/
+
+
+== Upgrading
+
+1. Uncompress the program archive in a new directory
+
+2. Copy your database settings (RAILS_ROOT/config/database.yml)
+   and your configuration file (RAILS_ROOT/config/configuration.yml)
+   into the new config directory
+   Note: before Redmine 1.2, SMTP configuration was stored in
+   config/email.yml. It should now be stored in config/configuration.yml. 
+
+3. Copy the RAILS_ROOT/files directory content into your new installation
+   This directory contains all the attached files.
+
+4. Copy the folders of the installed plugins and themes into new installation
+   Plugins must be stored in the [redmine_root]/plugins directory
+   Themes must be stored in the [redmine_root]/public/themes directory
+
+   WARNING: plugins from your previous Redmine version may not be compatible
+   with the Redmine version you're upgrading to.
+
+5. 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`.
+
+6. Generate a session store secret
+   
+   Redmine stores session data in cookies by default, which requires
+   a secret to be generated. Under the new application directory run:
+     rake generate_secret_token
+   
+   DO NOT REPLACE OR EDIT ANY OTHER FILES.
+
+7. Migrate your database
+
+   If you are upgrading to Rails 2.3.14 as part of this migration, you
+   need to upgrade the plugin migrations before running the plugin migrations
+   using:
+     rake db:migrate:upgrade_plugin_migrations RAILS_ENV="production"
+   
+   Please make a backup before doing this! Under the new application
+   directory run:
+     rake db:migrate RAILS_ENV="production"
+   
+   If you have installed any plugins, you should also run their database
+   migrations using:
+     rake db:migrate_plugins RAILS_ENV="production"
+   
+8. Clear the cache and the existing sessions by running:
+     rake tmp:cache:clear
+     rake tmp:sessions:clear
+
+9. Restart the application server (e.g. mongrel, thin, passenger)
+
+10. Finally go to "Administration -> Roles & permissions" to check/set permissions
+    for new features, if any
+
+== References
+
+* http://www.redmine.org/wiki/redmine/RedmineUpgrade