Tracks is a GTD™ web application, built with Ruby on Rails https://www.getontracks.org/
Find a file
Luke Melia 35ae5fc431 Next step in upgrading Tracks to Rails 2.2. Some highlights:
* Ran rake rails:update
* Added old actionwebservice framework
* Updated RSpec and RSpec-Rails
* Removed asset_packager plugin (not compatible, Scott no longer maintaining), and replaced with bundle_fu. See the bundle_fu README for more info.
* Hacks to UJS and ARTS plugins, which are no longer supported. Probably should move off both UJS and RJS.
* Hack to flashobject_helper plugin (upgrade to Rails 2.2-compatible version if/when it comes out.)
* Hack to skinny-spec plugin, for Rails 2.2 compatibility. Should check for official release.
* Hacks to resource_feeder plugin, for Rails 2.2 compatibility. Should check for official release (not likely) or move off it.
* Addressed some deprecation warnings. More to come.
* My mobile mime type hackery is no longer necessary with new Rails features. Yay!
* Updated environment.rb.tmpl with changes

TODO:
* Restore view specs marked pending
* Fix failing integration tests.
* Try selenium tests.
* Investigate OpenID support.
* Address deprecation warnings.
* Consider moving parts of environment.rb to initializers
* Address annoying config.gem warning about highline gem
2008-11-30 00:34:15 -05:00
app Next step in upgrading Tracks to Rails 2.2. Some highlights: 2008-11-30 00:34:15 -05:00
config Next step in upgrading Tracks to Rails 2.2. Some highlights: 2008-11-30 00:34:15 -05:00
db fix migration to fill the updated_at column. The rss feeds need a filled column. Fixes #794 2008-11-26 10:53:00 +01:00
doc update changelog 2008-10-28 21:09:54 +01:00
lib Next step in upgrading Tracks to Rails 2.2. Some highlights: 2008-11-30 00:34:15 -05:00
log.tmpl Removed superfluous 'tracks' directory at the root of the repository. 2008-05-20 21:28:26 +01:00
public Next step in upgrading Tracks to Rails 2.2. Some highlights: 2008-11-30 00:34:15 -05:00
script Next step in upgrading Tracks to Rails 2.2. Some highlights: 2008-11-30 00:34:15 -05:00
spec Next step in upgrading Tracks to Rails 2.2. Some highlights: 2008-11-30 00:34:15 -05:00
stories Next step in upgrading Tracks to Rails 2.2. Some highlights: 2008-11-30 00:34:15 -05:00
test Next step in upgrading Tracks to Rails 2.2. Some highlights: 2008-11-30 00:34:15 -05:00
vendor Next step in upgrading Tracks to Rails 2.2. Some highlights: 2008-11-30 00:34:15 -05:00
.gitignore Next step in upgrading Tracks to Rails 2.2. Some highlights: 2008-11-30 00:34:15 -05:00
Rakefile Removed superfluous 'tracks' directory at the root of the repository. 2008-05-20 21:28:26 +01:00
README add recurring todos to tracks 2008-07-19 20:27:45 +02:00

# Tracks: a GTD(TM) web application, built with Ruby on Rails

* Project homepage: http://www.rousette.org.uk/projects/
* GitHub: http://github.com/bsag/tracks/
* Trac (for bug reports and feature requests): http://dev.rousette.org.uk/report/6
* Wiki (community contributed information): http://www.rousette.org.uk/projects/wiki/
* Forum: http://www.rousette.org.uk/projects/forums/
* Mailing list: http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
* Original developer: bsag (http://www.rousette.org.uk/)
* Contributors: http://dev.rousette.org.uk/wiki/Tracks/Contributing/Contributors
* Version: 1.6
* Copyright: (cc) 2004-2008 rousette.org.uk.
* License:  GNU GPL

**An important note for version 1.6: OpenID support is broken in this release. The fix isn't trivial because of changes to the `ruby-openid` gem, so we wanted to get this version out now and fix OpenID for the next release. If you depend on OpenID integration, we recommend waiting until the next release.**

All the documentation for Tracks can be found within the /doc directory. It contains a manual in HTML (manual.html) or PDF format (manual.pdf), and this includes full instructions for both new installations and upgrades from older installations of Tracks. The instructions might appear long and intimidatingly complex, but that is mostly because of the number of different platforms supported, and the different configurations which can be used (e.g. running Tracks on your local computer or on a remote server). If you choose the appropriate section for your situation (installation vs. upgrade), and use the easiest (recommended) method, you should find the instructions easy to follow. If you encounter problems, try searching the wiki, forum or mailing list (URLs above), and ask a question if you cannot find a solution to your problem.

For those upgrading, change notes are available in /doc/CHANGELOG. If you are thinking about contributing towards the development of Tracks, please read /doc/README_DEVELOPERS for general information, or /doc/tracks_api_wrapper.rb for information on Tracks' API.

While fully usable for everyday use, Tracks is still a work in progress. Make sure that you take sensible precautions and back up all your data frequently, taking particular care when you are upgrading.

Enjoy being productive!