Jun 2005 05

Tracks 1.03 beta

Version: 1.03 beta
File:
Subversion URL: http://www.rousette.org.uk/svn/tracks-repos/tags/tracks-1.03beta
I think we’re at a point now where I’m happy to release Tracks 1.03 beta, especially as we’re at the auspicious revision 100! You can either download the zip file, or use Subversion to check out the tag.

Please note that this shouldn’t be used for your precious data—this is a beta release to bash out the remaining bugs and glitches on different systems. I would put it in a different directory to your own version of Tracks (if you have one), and make a new database to hold the test data. When people have had a chance to report any remaining bugs, I’ll clear everything up and make a proper production release.

I haven’t updated the installation instructions yet, but it’s similar to the previous version. There are, however, a few things to bear in mind:

1. Don’t forget to copy config/database.yml.tmpl and config/settings.yml.tmpl to config/database.yml and config/settings.yml.
1. There’s a new option in config/settings.yml, so don’t forget to edit that, or you’ll get an error involving <%= staleness(item.created) %>
1. I really do recommend making a new database to test this, so use the appropriate tracks_1.0.3_[databaseformat].sql file for your chosen database (mysql, sqlite or postgresql) to set up the tables, and then, if you want, use the tracks_1.0.3_content.sql to add some test content.

I’m looking forward to getting your feedback (see doc/CHANGENOTES.txt for all the new goodies). I’m particularly interested in how it fares on other platforms (not MacOSX), and other databases (i.e. SQLite and PostgreSQL), and how you find the speed. I’ve taken out caching for now, so let me know if you find it annoyingly slow. If you have any issues, check on Trac to see if anyone has already reported it, and if not, open a new ticket here.

Thanks!

7 Comments

Very cool! Lots of AJAX fun and some nice usability improvements.

Ah. Lovely neat redesign.

I don’t think Ruby on Rails and I are meant to be. I can never install anything correctly on my web server.

I got everything uploaded and just end up getting errors (500)  when I go to /login/signup/. /login/ loads the login page, though.

Well, I updated some stuff and now I’m able to use it using WEBrick, but I’d like to use Apache. Unless there’s some way I can always leave WEBrick running—I turn it on through SSH, but once I close the SSH connection, WEBrick ends.

So is there a way I can somehow set WEBrick to continuously run? Yeah, I’m new. haha

chris rhee: If you’re able to use it with WEBrick, that suggests that your database is OK, and you’ve got the basic setup configured. Some things to check:

1. Do you have the rewrite module enabled? LoadModule rewrite_module modules/mod_rewrite.so

2. Do you have the DocumentRoot for your domain pointed at the tracks/public directory? You might need to set up a VirtualHost (as described here)

3. There’s a new route for signup, so you can just load Does this work?

 

As for running WEBrick continuously, you could start it via a cron job, or run it (via ssh) in a screen session, then detach the screen, but those are both clunky. It would be better to get Apache running. Get back to me if you have any more problems.
——-

I am trying to setup a command in fluordesign.com’s cron. The command runs perfectly in ssh:

/home/tigdsg/tig/script/server -d - 8050

But if I try to setup a cron for it, or even make cron call a script with this command I can only get:

/usr/bin/env: ruby: No such file or directory

Luis: I think that you probably need something like:


/full/pathto/ruby /home/tigdsg/tig/script/server -d -8050

Cron needs to run ruby to run the script and can’t find it. By the way, you know that Tracks 1.04 is out now? Full of GTD goodness wink

Name:

Email (not shown on page):

Location (optional):

URL:

Remember my personal information

Notify me of follow-up comments?

Please enter the word you see in the image below: