Andreas/tracks
1
0
Fork 0
mirror of https://github.com/TracksApp/tracks.git synced 2025-09-21 21:40:48 +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/
1167 commits 34 branches 36 tags 27 MiB
Find a file
Reinier Balt 13db454e8a update documentation and set version to 1.7.1 for release
2010-04-11 16:50:13 +02:00
app add checks on valid date for due and show from in edit and create todo form. Fixes #982. 2010-04-04 19:34:24 +02:00
config update documentation and set version to 1.7.1 for release 2010-04-11 16:50:13 +02:00
db update sqlite sample database to latest migrations 2009-02-09 11:13:56 +01:00
doc update documentation and set version to 1.7.1 for release 2010-04-11 16:50:13 +02:00
lib Move site-specific configuration out of environment.rb into a YAML file. This allows us to ship environment.rb with Tracks. Fixes #813. 2009-02-01 14:47:05 -05:00
log.tmpl Removed superfluous 'tracks' directory at the root of the repository. 2008-05-20 21:28:26 +01:00
public Fix #896. Tidied styling of notes (attached to action and free-standing project notes) so that basic Textile markup shows up and looks attractive. You can now use *bold*, _italics_, ordered lists (#), unordered lists (*), and H1 (h1.) and H2 (h2.) headers can all be used, along with Textile links. 2009-05-17 14:13:52 +01:00
script Next step in upgrading Tracks to Rails 2.2. Some highlights: 2008-11-30 00:34:15 -05:00
spec fix failing spec 2009-03-01 22:18:03 +01:00
stories Next step in upgrading Tracks to Rails 2.2. Some highlights: 2008-11-30 00:34:15 -05:00
test Don't set time to UTC for midnight in test. 2009-09-25 08:54:54 +02:00
vendor fix crlf issue 2009-02-07 21:26:43 +01:00
.gitignore Move site-specific configuration out of environment.rb into a YAML file. This allows us to ship environment.rb with Tracks. Fixes #813. 2009-02-01 14:47:05 -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 update documentation and set version to 1.7.1 for release 2010-04-11 16:50:13 +02: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.1
* Copyright: (cc) 2004-2010 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!