Andreas/tracks
1
0
Fork 0
mirror of https://github.com/TracksApp/tracks.git synced 2025-12-16 23:30:12 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
Tracks is a GTD™ web application, built with Ruby on Rails https://www.getontracks.org/
1074 commits 31 branches 36 tags 32 MiB
Find a file
Luke Melia a1a8260f10 Added an example of capistrano deployment recipes for deploying to a remote web host running Phusion Passenger (aka mod_rails), which is probably the easiest Rails deployment environment to configure.
2009-01-04 17:14:03 -05:00
app Update footer links for new website location 2009-01-03 17:57:57 -05:00
config Added an example of capistrano deployment recipes for deploying to a remote web host running Phusion Passenger (aka mod_rails), which is probably the easiest Rails deployment environment to configure. 2009-01-04 17:14:03 -05:00
db Minor updates to the example db. 2008-12-14 11:43:34 +00:00
doc Pulled in the changes to the manual. 2008-12-30 19:15:16 +00:00
lib Added an example of capistrano deployment recipes for deploying to a remote web host running Phusion Passenger (aka mod_rails), which is probably the easiest Rails deployment environment to configure. 2009-01-04 17:14:03 -05:00
log.tmpl Removed superfluous 'tracks' directory at the root of the repository. 2008-05-20 21:28:26 +01:00
public Merge branch 'gorn/master' 2008-12-14 15:34:24 +00:00
script Next step in upgrading Tracks to Rails 2.2. Some highlights: 2008-11-30 00:34:15 -05:00
spec Change mobile login form to post to proper URL for OpenID login. Resolves #810. 2009-01-02 02:22:06 -05:00
stories Next step in upgrading Tracks to Rails 2.2. Some highlights: 2008-11-30 00:34:15 -05:00
test Added a fix for a failing functional test which concerned the javascript popup window to warn when a new context added in new action form. 2008-12-26 19:47:13 +00:00
vendor Fixed webrat/core.rb to solve problem with Ubuntu, as documented here: 2008-12-26 17:55:09 +00:00
.gitignore Added an example of capistrano deployment recipes for deploying to a remote web host running Phusion Passenger (aka mod_rails), which is probably the easiest Rails deployment environment to configure. 2009-01-04 17:14:03 -05:00
.gitmodules Included the tracks_manual repository as a git submodule within doc/manual. 2008-12-30 19:05:41 +00:00
Capfile Added an example of capistrano deployment recipes for deploying to a remote web host running Phusion Passenger (aka mod_rails), which is probably the easiest Rails deployment environment to configure. 2009-01-04 17:14:03 -05:00
Rakefile Removed superfluous 'tracks' directory at the root of the repository. 2008-05-20 21:28:26 +01:00
README Added note about getting doc/manual submodule to README. 2009-01-01 11:53:22 +00:00

README 

# 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-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.

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 update --init 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!