Andreas/tracks: Tracks is a GTD™ web application, built with Ruby on Rails

mirror of https://github.com/TracksApp/tracks.git synced 2025-12-24 03:00:12 +01:00

Tracks is a GTD™ web application, built with Ruby on Rails https://www.getontracks.org/

getting-things-done gtd productivity rails ruby todo tracks

Find a file

bsag 4fb4a98bc8 Merge branch 'master' into clinton/master * master: (40 commits) Updated the manual in HTML, PDF and .tex format. Minor updates to the example db. set version to 1.7RC update version in template update changelog OpenSearch support. update the sample sqlite databases and update sample content sql. Solves #802 forgot ot change one version to 1.7 update documentation for 1.7rc release No point in changing the name of the OpenID identity column in users table. Use the existing one. show recurrence pattern in :title of a recurring todo. Needed slight refactoring to make it happen Re-write OpenID code to use new authentication plugin. Tested to work! Upgraded to open_id_authentication plugin at `00d8bc7f97` and unpacked ruby-openid gem version 2.1.2. remove old compressed js and css from the asset_packager plugin that we don't use anymore applied the patches from Jakub to improve the mobile html adds test for changing context on a todo in tag view. Resolves #762 Add testcase where changing the name of a project should be reflected in the default project name. resolves #756 add testcase for deleting a user. Resolves #734 implement suggestions for search in #787 fix failing tests ...		2008-12-14 15:08:28 +00:00
app	Merge branch 'master' into clinton/master	2008-12-14 15:08:28 +00:00
config	update version in template	2008-12-11 16:50:14 +01:00
db	Minor updates to the example db.	2008-12-14 11:43:34 +00:00
doc	Updated the manual in HTML, PDF and .tex format.	2008-12-14 12:01:02 +00: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	remove old compressed js and css from the asset_packager plugin that we don't use anymore	2008-12-05 15:58:20 +01: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	No point in changing the name of the OpenID identity column in users table. Use the existing one.	2008-12-08 18:51:33 -05:00
vendor	Upgraded to open_id_authentication plugin at `00d8bc7f97` and unpacked ruby-openid gem version 2.1.2.	2008-12-08 00:44:09 -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	set version to 1.7RC	2008-12-11 16:59:48 +01:00

README

# 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.7RC
* Copyright: (cc) 2004-2008 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.

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!