Tracks is a GTD™ web application, built with Ruby on Rails https://www.getontracks.org/
Find a file
Eric Allen a022f449c1 Fixed failing tests
- Some fixtures added by Erik Ordway broke tests
- message:// links had an edge case I broke with 68701ada
- One test had a hard-coded id that changed

Closes #1019
2010-04-09 09:34:57 -04:00
app Fixed failing tests 2010-04-09 09:34:57 -04:00
artwork Move dependency drop target into image 2010-03-07 16:21:52 -05:00
config Sanitize output well, but entity-ize < and > in notes 2010-04-07 10:06:46 -04:00
db Blank DB with pre-defined contexts for easier start 2010-04-02 09:46:20 -04:00
doc update CHANGELOG to reflect the changes made in 1.8devel 2009-04-16 09:52:35 +02:00
features refactor dependency cucumber feature to use css. This saves us the extra id on the todo element that I added in the previous commit. 2010-03-25 16:34:01 +01:00
lib add rake task to run selenium cucumber features with rake cucumber:selenium 2010-03-08 20:36:55 +01:00
log.tmpl Removed superfluous 'tracks' directory at the root of the repository. 2008-05-20 21:28:26 +01:00
public AJAX loading of context names 2010-04-04 22:30:29 -04:00
script update cucumber 2010-01-13 20:39:28 +01:00
spec Fixed failing tests 2010-04-09 09:34:57 -04:00
test Fixed failing tests 2010-04-09 09:34:57 -04:00
vendor Get rid of in_place_editing plugin 2010-03-14 16:50:24 -04:00
.gitignore No more bundle-fu 2010-03-14 16:18:13 -04:00
.gitmodules Included the tracks_manual repository as a git submodule within doc/manual. 2008-12-30 19:05:41 +00:00
Capfile Modified capfile to allow plugins 2009-04-01 04:00:38 +08:00
Rakefile Removed superfluous 'tracks' directory at the root of the repository. 2008-05-20 21:28:26 +01:00
README bump version numbers to 1.7 2009-02-26 20:45:21 +01:00

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

* Project homepage: http://getontracks.org/
* GitHub: http://github.com/bsag/tracks/
* Assembla space (for bug reports and feature requests): http://www.assembla.com/spaces/tracks-tickets/tickets
* Wiki (community contributed information): http://getontracks.org/wiki/
* Forum: http://getontracks.org/forums/
* Mailing list: http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
* Original developer: bsag (http://www.rousette.org.uk/)
* Contributors: http://getontracks.org/wiki/Tracks/Contributing/Contributors
* Version: 1.7
* Copyright: (cc) 2004-2009 rousette.org.uk.
* License:  GNU GPL

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.

If you checked out Tracks from the GitHub repository, the manual is not provided by default and is in its own git submodule. To checkout the manual's source files, type "git submodule init doc/manual & git submodule update doc/manual". From then on, you should be able to issue the command "git pull" in the doc/manual directory to update the manual with the latest changes.

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!