Eric Scalf
Thu, 22 Dec 2005 @ 11:29 ¶

John’s tutorial is great, but in my opinion it’s a little overkill.  I’ve written a tutorial that uses just MySQL, Ruby, and Rails to get Tracks working.  No extra webserver neccesary.  Although I’m not much of a tutorial writer, I figure it came out clear enough.

Now if I could just find a way to get rid of the pesky command prompt window.

Thanks for the great software!

-Eric

Matt Bivins
Fri, 21 Apr 2006 @ 16:21 ¶

I really wish that someone would make a movie like that for the Mac. I know that it’s supposed to be ridiculously easy for Macs and Linux. I guess that makes me an idiot. I just can’t get Tracks to work. Even sadder, I’m hosting with a server that serves up Ruby on Rails… and I’ve tried getting Tracks up and running any way I can (on my Mac, and the server) and am just missing basic concepts that I guess others just have, locked down. It’s really cutting into my Battlestar Galactica watching time… does anyone have any os x (Tiger) tips for a new-new-newbie?

Matt Bivins
Wed, 26 Apr 2006 @ 19:16 ¶

bsag: Thanks very much! I spent an hour or so in the command line following the Hivelogic narrative on the os X installation page (in the wiki). Things seemed to go fairly smoothly… I think that the problems started when I tried to actually install Tracks. I now should have Ruby, Rails, a mySQL server, and some other goodies available to me on my iMac; I just get flummoxed by the “rail migrate” business, and setting up the databases. I’d appreciate any other help, for sure! Thanks in advance.

bsag
Sat, 29 Apr 2006 @ 15:26 ¶

Matt Bivins: OK. Well if you follow the instructions in installation.html very carefully, you should be OK. But what you need to do is to unzip the tracks package somewhere convenient. I suggest /Users/yourusername/Sites/tracks (I’ll shorten this to ~/Sites/tracks from now on). Then you need to copy the template files: copy log.tmpl to log (so that the folder log contains apache.log, development.log, production.log and test log), copy config/database.yml.tmpl to config/database.yml and config/environment.rb.tmpl to config/environment.rb.

Then you need to open up database.yml and fill in the details of your MySQL database name (you need to create one first and call it, for example, tracks-1041), MySQL username and password. Fill in the same details for the development and production sections and leave the test section blank. In normal use, we’ll be running Tracks under production mode, so only the production details will be needed, but to set it up we’ll need development mode.

Now, open up the Terminal application (it’s in Application/Utilities/Terminal). Type:

cd ~/Sites/tracks; rake migrate

If that generates some obscure error, delete the MySQL database you created and create a fresh one. Then type:

rake db_schema_import

Check the database to make sure that it has some tables set up inside it. If so, all should be well. You should be able to start the server up with Locomotive using the control panel, and from there you need to visit the signup page (http://yoururl/signup) to make some users.

Ted: If you have sqlite3 working, then just use the sqlite database I provided (db/tracks-104.db). There’s then no need to run rake migrate. Just make sure that you’ve put the correct full path to the database in the database: line of database.yml.

Hope that helps!

jonny blaze
Fri, 12 May 2006 @ 16:37 ¶

incase you’re behind a firewall like i was, see the “if all else fails” section on here http://wiki.rubyonrails.com/rails/pages/GemRails/versions/21

David
Mon, 25 Jun 2007 @ 17:38 ¶

Before I get started with this, can anyone tell me if I’ll be able to install Tracks behind my companies firewall, with a “locked” down corporate PC (Windows XP)?
Thanks.

Gurrah
Sat, 1 Mar 2008 @ 11:39 ¶

It is good that someone writes articles which really matters something. Thank you for this article, it�s full of knowledge which is hard to find in tons of rubbish in our famous world wide web. Regards and good luck!