Tracks is a GTD™ web application, built with Ruby on Rails https://www.getontracks.org/
Find a file
2012-09-26 22:09:20 -04:00
app convert CSS to Sass for better asset references 2012-09-26 14:16:53 -04:00
config Try the cache_digests gem for Tracks 2012-09-02 15:13:28 +02:00
db add tolk to Tracks for easy management of translations. Limited to development 2012-07-18 14:58:24 +02:00
doc update project-meta links in README and CHANGELOG 2012-08-27 20:23:19 -04:00
features force english prefered language in firefox test profile 2012-07-22 10:45:02 +02:00
lib Make sure that changing tags (i.e. toggle star) touches the taggable (todo) to invalidate cache. Make sure _context is cached different for _context of active todos and _context of tagged todos and _context in tickler 2012-09-02 15:13:29 +02:00
public add swf to asset pipeline. Fixes #1311 2012-07-16 17:38:44 +02:00
script initial upgrade to rails 3.2.3 2012-04-30 13:56:33 +02:00
test Update the fixture data to work with PostgreSQL 2012-08-28 08:39:52 -05:00
vendor update to jquery-ui-1.8.23 2012-08-31 15:15:11 +02:00
.gitignore update .gitignore rules for rails3.1 asset pipeline 2012-09-26 22:09:20 -04:00
.gitignore.rails2 initial upgrade to rails 3.2.3 2012-04-30 13:56:33 +02:00
.yardopts Yardoc - show private and protected methods in api doc 2011-10-24 21:40:18 +02:00
Capfile Modified capfile to allow plugins 2009-04-01 04:00:38 +08:00
config.ru initial upgrade to rails 3.2.3 2012-04-30 13:56:33 +02:00
Gemfile Move to forked cache_digests for ruby 1.8.7 compatibility 2012-09-02 15:13:28 +02:00
Gemfile.lock Move to forked cache_digests for ruby 1.8.7 compatibility 2012-09-02 15:13:28 +02:00
Rakefile initial upgrade to rails 3.2.3 2012-04-30 13:56:33 +02:00
README.md update project-meta links in README and CHANGELOG 2012-08-27 20:23:19 -04:00

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

Code Climate

More documentation for Tracks can be found within the /doc directory

The manual 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.

The wiki has a lot of user contributed installation HOWTOs for various webhosts, specific OS's and more.

If you are thinking about contributing towards the development of Tracks, please read /doc/README_DEVELOPERS for general information. Also you can find some information on development, testing and contributing on the wiki.

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!