annotate .svn/pristine/99/993669603cb0d8da03a8d1aab8b814b747a7d19c.svn-base @ 1082:997f6d7738f7 bug_531

In repo controller entry action, show the page for the file even if it's binary (so user still has access to history etc links). This makes it possible to use the entry action as the default when a file is clicked on
author Chris Cannam <chris.cannam@soundsoftware.ac.uk>
date Thu, 22 Nov 2012 18:04:17 +0000
parents cbb26bc654de
children
rev   line source
Chris@909 1 == Redmine upgrade
Chris@909 2
Chris@909 3 Redmine - project management software
Chris@909 4 Copyright (C) 2006-2011 Jean-Philippe Lang
Chris@909 5 http://www.redmine.org/
Chris@909 6
Chris@909 7
Chris@909 8 == Upgrading
Chris@909 9
Chris@909 10 1. Uncompress the program archive in a new directory
Chris@909 11
Chris@909 12 2. Copy your database settings (RAILS_ROOT/config/database.yml)
Chris@909 13 and your configuration file (RAILS_ROOT/config/configuration.yml)
Chris@909 14 into the new config directory
Chris@909 15 Note: before Redmine 1.2, SMTP configuration was stored in
Chris@909 16 config/email.yml. It should now be stored in config/configuration.yml.
Chris@909 17
Chris@909 18 3. Copy the RAILS_ROOT/files directory content into your new installation
Chris@909 19 This directory contains all the attached files.
Chris@909 20
Chris@909 21 4. Copy the folders of the installed plugins and themes into new installation
Chris@909 22
Chris@909 23 5. Generate a session store secret
Chris@909 24
Chris@909 25 Redmine stores session data in cookies by default, which requires
Chris@909 26 a secret to be generated. Under the new application directory run:
Chris@909 27 rake generate_session_store
Chris@909 28
Chris@909 29 DO NOT REPLACE OR EDIT ANY OTHER FILES.
Chris@909 30
Chris@909 31 6. Migrate your database
Chris@909 32
Chris@909 33 If you are upgrading to Rails 2.3.14 as part of this migration, you
Chris@909 34 need to upgrade the plugin migrations before running the plugin migrations
Chris@909 35 using:
Chris@909 36 rake db:migrate:upgrade_plugin_migrations RAILS_ENV="production"
Chris@909 37
Chris@909 38 Please make a backup before doing this! Under the new application
Chris@909 39 directory run:
Chris@909 40 rake db:migrate RAILS_ENV="production"
Chris@909 41
Chris@909 42 If you have installed any plugins, you should also run their database
Chris@909 43 migrations using:
Chris@909 44 rake db:migrate_plugins RAILS_ENV="production"
Chris@909 45
Chris@909 46 7. Clean up
Chris@909 47
Chris@909 48 Clear the cache and the existing sessions by running:
Chris@909 49 rake tmp:cache:clear
Chris@909 50 rake tmp:sessions:clear
Chris@909 51
Chris@909 52 8. Restart the application server (e.g. mongrel, thin, passenger)
Chris@909 53
Chris@909 54 9. Finally go to "Administration -> Roles & permissions" to check/set permissions
Chris@909 55 for new features, if any
Chris@909 56
Chris@909 57 == Notes
Chris@909 58
Chris@909 59 * Rails 2.3.14 is required for versions 1.3.x.
Chris@909 60
Chris@909 61 == References
Chris@909 62
Chris@909 63 * http://www.redmine.org/wiki/redmine/RedmineUpgrade