From 24ebe27d64f987a24cdc559344e5fe1212815800 Mon Sep 17 00:00:00 2001 From: Reinier Balt Date: Mon, 18 Feb 2013 19:47:31 +0100 Subject: [PATCH] add upgrade instructions for 2.1.4 --- doc/upgrading.textile | 42 +++++------------------------------------- 1 file changed, 5 insertions(+), 37 deletions(-) diff --git a/doc/upgrading.textile b/doc/upgrading.textile index 1e30bd02..e47efccc 100644 --- a/doc/upgrading.textile +++ b/doc/upgrading.textile @@ -1,48 +1,16 @@ h1. Upgrading Tracks -h2. Upgrading from Tracks 2.1.x/2.2RC to 2.2 +h3. Upgrading from Tracks 2.1, 2.1.1, 2.1.2, 2.1.3 to 2.1.4 -This release adds a variety of new features and bugfixes to Tracks. - -The database will need to be migrated as part of the install. - -To upgrade: -# Back up your existing database and installation of Tracks -# Install Tracks 2.2 in a new directory -# Copy over the configuration from your previous Tracks installation. If using SQLite3, copy the old database into the new Tracks 2.2 directory. -# Check that you have all dependencies installed: @bundle install --without development test@ -# Run @bundle exec rake db:migrate RAILS_ENV=production@ to update your old database to the new schema. This is the point of no return. Make sure you have backups! -# The administrator email address shown on the signup page is now configured in @config/site.yml@. Edit your @config/site.yml@ and add an @admin_email@ option. See @config/site.yml.tmpl@ for an example. -# If you're using mysql, change the database adapter from @mysql@ to @mysql2@ in your @config/database.yml@ file. The @mysql2@ adapter replaces the @mysql@ adapter in Rails 3.2 -# Precompile your static assets (css, javascript, etc.) by running @bundle exec rake assets:precompile@ -# Run @bundle exec rails server -e production@ inside your Tracks 2.2 directory to start up Tracks 2.2. -# Once you are happy that everything is working well, delete your old Tracks directory. - -h2. Upgrading from Tracks 2.1.1 to 2.1.2 - -The purpose of this release is to address several security vulnerabilities that were recently discovered in Rails. For details about the contents of the release, please see the "difference view":https://github.com/TracksApp/tracks/compare/v2.1.1...v2.1.2 on GitHub. +The purpose of this release is to address several security vulnerabilities that were recently discovered in Rails. For details about the contents of the release, please see the "difference view":https://github.com/TracksApp/tracks/compare/v2.1.1...v2.1.4 on GitHub. There are no changes done to the database, it is therefore not necessary to run the migrations. To upgrade: # Back up your existing database and installation of Tracks -# Install Tracks 2.1.2 in a new directory -# Copy over the configuration from your previous Tracks installation. If using SQLite3, copy the old database into the new Tracks 2.1.2 directory. +# Install Tracks 2.1.4 in a new directory +# Copy over the configuration from your previous Tracks installation. If using SQLite3, copy the old database into the new Tracks 2.1.4 directory. # Check that you have all dependencies installed and up-to-date: @bundle install --without development test@ -# Run @bundle exec script/server@ inside your Tracks 2.1.2 directory to start up Tracks 2.1.2. -# Once you are happy that everything is working well, delete your old Tracks directory. - - -h2. Upgrading from Tracks 2.1 to 2.1.1 - -This release is a bugfix release. For details about the fixes, see the "difference view":https://github.com/TracksApp/tracks/compare/v2.1...v2.1.1 on Github. - -There are no changes done to the database, it is therefore not necessary to run the migrations. For upgrading: - -# Back up your existing database and installation of Tracks -# Install Tracks 2.1.1 in a new directory -# Copy over the configuration from your previous Tracks installation. If using SQLite3, copy the old database into the new Tracks 2.1 directory. -# Check that you have all dependencies installed and up-to-date: @bundle install --without development test@ -# Run @bundle exec script/server@ inside your Tracks 2.1.1 directory to start up Tracks 2.1.1. +# Run @bundle exec script/server@ inside your Tracks 2.1.4 directory to start up Tracks 2.1.4. # Once you are happy that everything is working well, delete your old Tracks directory. h2. Upgrading from Tracks 2.0 or 2.1RC1 to 2.1