bsag
Tue, 8 Nov 2005 @ 09:02 ¶

I don’t have an account on Dreamhost, so I can’t test it. However, I don’t know if the RewriteBase liine is needed anymore. Rails now has routes which handle much of the URL rewriting, so in most circumstances, the standard .htaccess should work.

I took a look at the comments on qdot’s page, and there’s one from Carl Youngblood as follows:

“I figured out my problem. All directories in which your rails installation goes have to be chmodded to 755 permissions. My domain’s directory was set to 775, and it caused Apache to fail when trying to run my CGI scripts.”

Might that solve your problem?

Michael
Mon, 10 Apr 2006 @ 22:01 ¶

I have Tracks running on Dreamhost. The only hard part was waiting for them to create the DB. They said 10 minutes, but it ended up being almost 10 hours.

Once that was done, it was smooth sailing. Of course, ‘rake migrate’ did not work, so I have to use ‘rake db_schema_import’ and it worked great.

Hemant Gupta
Tue, 20 Jun 2006 @ 14:48 ¶

I got it running on Windows, so I decided to try moving it to a site hosted by asmallorange.com.  The comments in the dreamhost discussion made me think that it was too slow to be useful.

Of course everything went smoothly on asmallorange all the way in the installation.html file until you get to the part about launching the browser.  That part of the instruction only applies to local installs.  Can anyone give me guidance about how to launch it off a webhost?

brian
Tue, 27 Jun 2006 @ 11:25 ¶

I just went through the process of installing Tracks on Dreamhost and it’s actually gotten quite a bit simpler.  And I’m strictly a desktop coder, I came to this with no knowledge of Ruby or Rails. Here’s my version:

1) Ruby on Rails is installed on Dreamhost servers by default, so skip that section of qDot’s tutorial.  Jump to the “Installing Tracks” section.  Do the first 5 steps.

2) Change to your tracks directory and create the “log” directory - otherwise, “rake migrate” will fail.  you can run “rake—trace migrate” to get more detail in case of errors, which is how I found that one.

3) run “rake migrate” to load up the schemas, as outlined in tracks/installation.html.

4) access your tracks install at http://yourhost.com/tracks/signup to give yourself a login

3) change the supplied .htaccess file in tracks/public to use dispatch.fcgi by default instead of dispatch.cgi - otherwise performance is quite poky!

And that’s it!  I now have a lovely installation of Tracks - and well done, bsag, it’s really a nicely implemented bit of code!

Andrea
Sat, 15 Jul 2006 @ 11:04 ¶

If anyone is interested, I’ve found a hosted installation of tracks at
http://tracks.tra.in/

free for everyone to use.

bsag
Wed, 27 Sep 2006 @ 17:49 ¶

Thanks, Frederik! You could add a link to your tutorial on the wiki if you like.

mahalie
Sat, 14 Oct 2006 @ 02:12 ¶

I guess third time’s a charm. Thanks to Frederik’s install directions. Follow them exactly. I was confused at first seeing the ‘Welcome Aboard’ page and a weird error under Application Enviro: ‘Recognition failed for “/rails/info/properties”’ but ignored it, deleted index.html as instructed and my app is up and working. bsag, YOU ROCK MY WORLD!

Stuart
Mon, 23 Jul 2007 @ 12:54 ¶

Just used Frederik’s instructions along with the standard Tracks install notes and everything work. I tried this previously and could not get it to work, so thanks to all.