Andreas/tracks
1
0
Fork 0
mirror of https://github.com/TracksApp/tracks.git synced 2025-09-22 05:50:47 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions
Tracks is a GTD™ web application, built with Ruby on Rails https://www.getontracks.org/
1910 commits 35 branches 36 tags 27 MiB
Find a file
Matt Rogers f69e3e42b0 Update the dependencies so that the tests will run 
There were several places where newer versions of gems were being
pulled.  Those newer versions were breaking the functional tests and the
cucumber features.

Go back to known working versions of the gems that were causing failures
2011-08-19 21:34:56 -05:00
app improve tests for preferences and fix a pending cucumber step 2011-08-19 12:51:06 +02:00
config Just use actionwebservice in the environment file 2011-08-19 21:34:56 -05:00
db make sure toggle_check and deleting of todos, recurring_todos and projects work in the new done views 2011-07-09 17:21:36 +02:00
doc fix #922. You can now mark a todo complete from the tickler. Also fixed some small aasm corner cases found by this change 2011-08-18 17:15:00 +02:00
features improve tests for preferences and fix a pending cucumber step 2011-08-19 12:51:06 +02:00
lib get the done view on a context and a project 2011-07-09 17:21:34 +02:00
log.tmpl Removed superfluous 'tracks' directory at the root of the repository. 2008-05-20 21:28:26 +01:00
public add cucumber scenarios for new preferences 2011-08-18 12:48:59 +02:00
script update tree with missing 2.3.11 files or files that were not updated 2011-05-31 19:30:35 +02:00
spec fix failing specs 2011-08-16 11:49:04 +02:00
test improve tests for preferences and fix a pending cucumber step 2011-08-19 12:51:06 +02:00
vendor Remove the vendored gems 2011-08-19 21:34:56 -05:00
.gitignore fix corner case that were failing the cucumber tests. On the calendar page at the end of the month, a todo may occur twice on the page. This was not taken into account for update an destroy 2011-04-30 17:57:36 +02: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
Gemfile Update the dependencies so that the tests will run 2011-08-19 21:34:56 -05:00
Gemfile.lock Update the dependencies so that the tests will run 2011-08-19 21:34:56 -05:00
Rakefile upgrade to rails 2.3.12 and fix deprecation warning and fix some version numbers of gems used for testing 2011-06-09 17:04:00 +02:00
README correct small errors in docs 2011-08-02 11:01:50 +02:00

README 

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

**IMPORTANT: Tracks is moving to a GitHub Organization to make it easier to continue administering the project. Development will soon cease at bsag/tracks and move to TracksApp/tracks. If you are currently pulling from bsag/tracks, please pull from TracksApp instead.**

`git clone git://github.com/TracksApp/tracks.git`

**The new home for Tracks is https://github.com/TracksApp/tracks**

* Project homepage: http://getontracks.org/
* Manual: http://TracksApp.github.com/tracks/
* Source at GitHub: http://github.com/TracksApp/tracks/
* Assembla space (for bug reports and feature requests): http://www.assembla.com/spaces/tracks-tickets/tickets
* Wiki (community contributed information): https://github.com/TracksApp/tracks/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: https://github.com/TracksApp/tracks/wiki/Contributors
* Version: 2.1devel
* Copyright: (cc) 2004-2011 rousette.org.uk.
* License:  GNU GPL

All the documentation for Tracks can be found within the /doc directory and at http://bsag.github.com/tracks/
The latter 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, or /doc/tracks_api_wrapper.rb for information on Tracks' API. Also you can find some information on development 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!