Andreas/tracks
1
0
Fork 0
mirror of https://github.com/TracksApp/tracks.git synced 2025-12-16 23:30:12 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Version 2.3.0

Browse source
This commit is contained in:
Dan Rice 2015-06-17 20:43:05 -04:00
parent 4c9685bb8b
commit 4070f4e03a
4 changed files with 7 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -9,7 +9,7 @@
* IRC channel: #tracks on Freenode * IRC channel: #tracks on Freenode
* Original developer: bsag (http://www.rousette.org.uk/) * Original developer: bsag (http://www.rousette.org.uk/)
* Contributors: https://github.com/TracksApp/tracks/wiki/Contributors * Contributors: https://github.com/TracksApp/tracks/wiki/Contributors
* Version: 2.3.rc1 * Version: 2.3.0
[![Build Status](https://travis-ci.org/TracksApp/tracks.svg?branch=2.3_branch)](https://travis-ci.org/TracksApp/tracks) [![Build Status](https://travis-ci.org/TracksApp/tracks.svg?branch=2.3_branch)](https://travis-ci.org/TracksApp/tracks)

2
config/initializers/tracks.rb
View file

@ -1,4 +1,4 @@
tracks_version='2.3.rc1' tracks_version='2.3.0'
# comment out next two lines if you do not want (or can not) the date of the # comment out next two lines if you do not want (or can not) the date of the
# last git commit in the footer # last git commit in the footer
#info=`git log --pretty=format:"%ai" -1` #info=`git log --pretty=format:"%ai" -1`

2
doc/CHANGELOG.md
View file

@ -1,4 +1,4 @@
## Version 2.3 ## Version 2.3.0
### New and changed features ### New and changed features
* Numerous bug fixes * Numerous bug fixes

8
doc/upgrading.md
View file

@ -1,16 +1,16 @@
# Upgrading Tracks # Upgrading Tracks
## Upgrading from Tracks 2.2 to 2.3 ## Upgrading from Tracks 2.2.x to 2.3.0
To upgrade: To upgrade:
1. Back up your existing database and installation of Tracks 1. Back up your existing database and installation of Tracks
2. Install Tracks 2.3 in a new directory. Or you can create a separate installation of 2.3 for testing purposes. 2. Install Tracks 2.3.0 in a new directory. Or you can create a separate installation of 2.3.0 for testing purposes.
3. Copy over the configuration from your previous Tracks installation. If using SQLite3, copy the old database into the new Tracks 2.3 directory. 3. Copy over the configuration from your previous Tracks installation. If using SQLite3, copy the old database into the new Tracks 2.3.0 directory.
4. Check that you have all dependencies installed: `bundle install --without development test` Or leave out the `--without development test` part if you intend to test or develop on this tree. 4. Check that you have all dependencies installed: `bundle install --without development test` Or leave out the `--without development test` part if you intend to test or develop on this tree.
5. 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! 5. 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!
6. Precompile your static assets (css, javascript, etc.) by running `bundle exec rake assets:precompile RAILS_ENV=production`. 6. Precompile your static assets (css, javascript, etc.) by running `bundle exec rake assets:precompile RAILS_ENV=production`.
7. Run `bundle exec rails server -e production` inside your Tracks 2.3 directory to start up Tracks. Or use `-e development` if you intend to try your changes and get more log info. 7. Run `bundle exec rails server -e production` inside your Tracks 2.3.0 directory to start up Tracks. Or use `-e development` if you intend to try your changes and get more log info.
Please note that if you intend to use Tracks with the built in webserver called WEBrick for production, you’ll need to change `config.serve_static_assets` to `true` in `config/environments/production.rb` in order for the images, stylesheets, and javascript files to be served correctly. Please note that if you intend to use Tracks with the built in webserver called WEBrick for production, you’ll need to change `config.serve_static_assets` to `true` in `config/environments/production.rb` in order for the images, stylesheets, and javascript files to be served correctly.