Tracks

Assistance Needed installing Tracks on Hostgator

2009-06-03T14:56:43+00:00

I need someone on the phone with me while I do this. If someone is willing to help, please write me at tedpenner on g mail

actionpack version error?

2009-05-18T00:29:05+00:00

I’ve been using Tracks v 1.6 on Dreamhost for a while now. Today I tried upgrading to 1.7. I followed the instructions, but when it comes time to update the database, I get:

username@yoda ~/tracks $ rake db:migrate RAILS_ENV=production—trace
(in /home/.hammacher/beetle_b/tracks)
** Invoke db:migrate (first_time)
** Invoke environment (first_time)
** Execute environment
rake aborted!
RubyGem version error: actionpack(2.1.0 not = 1.13.6)
/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:259:in `require_frameworks’
/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:133:in `process’
/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:112:in `send’
/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:112:in `run’
/home/username/tracks/config/environment.rb:20
/usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require’
/usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `require’
/usr/lib/ruby/gems/1.8/gems/activesupport-2.2.2/lib/active_support/dependencies.rb:153:in `require’
/usr/lib/ruby/gems/1.8/gems/activesupport-2.2.2/lib/active_support/dependencies.rb:521:in `new_constants_in’
/usr/lib/ruby/gems/1.8/gems/activesupport-2.2.2/lib/active_support/dependencies.rb:153:in `require’
/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/tasks/misc.rake:3
/usr/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:617:in `call’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:617:in `execute’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:612:in `each’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:612:in `execute’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:578:in `invoke_with_call_chain’
/usr/lib/ruby/1.8/monitor.rb:238:in `synchronize’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:571:in `invoke_with_call_chain’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:588:in `invoke_prerequisites’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:585:in `each’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:585:in `invoke_prerequisites’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:577:in `invoke_with_call_chain’
/usr/lib/ruby/1.8/monitor.rb:238:in `synchronize’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:571:in `invoke_with_call_chain’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:564:in `invoke’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:2019:in `invoke_task’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:1997:in `top_level’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:1997:in `each’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:1997:in `top_level’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:2036:in `standard_exception_handling’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:1991:in `top_level’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:1970:in `run’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:2036:in `standard_exception_handling’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:1967:in `run’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.3/bin/rake:31
/usr/bin/rake:19:in `load’
/usr/bin/rake:19

I’m not a Rails person. Any ideas?

(At the moment, I may try to install 1.6 on a local machine, copy the DB over. Upgrade locally. And then re-install from scratch on server and just move local DB over to host. But that’s a pain and I’m sure I’ll screw up…).

Server keeps stopping on bluehost (unix using cPanel)

2009-05-10T00:06:32+00:00

Hello,

I’m not familiar with RoR, but I do have a lot of programming experience.

That being said, I successfully installed tracks on my bluehost account (it runs cPanel), all through the SSH. However, the server keeps stopping shortly after I log out of the SSH and I was wondering if anyone had any tips on how to get the RoR server to stay alive?

Also, I’ve done enough RoR tutorials to see that many apps are accessed through the “/public” folder, but tracks doesn’t seem to use this method—it uses a port instead. Any way to change that so that tracks uses the /public directory sicne I’m having a lot more success getting my web server to allow access to those files.

thanks,

Tracks on Heroku howto

2009-05-06T21:27:33+00:00

heroku.com is a new way of hosting rails apps that takes away lots of the pain. I got a tracks installation up and running there, so I thought I’d pass on some info about what I did. It’s from memory, but I’ll try and cover the main points.

1) Register for heroku and get familiar with it. Take a look at the site and learn about the way it integrates so nicely with git. To use Heroku it helps to be familiar with rails and git, but it’s still easier than most rails deployments. You’ll have to install the heroku gem using “[sudo] gem install heroku”

2) checkout Tracks from github. I checked out the master branch a couple of days ago, and it seems to work fine for me.

3) Customise Tracks for heroku.
a) This is the key bit. Heroku runs your app on a read-only file system, so bundle-fu can’t write to the local directory like it wants. I worked around this by commenting out the <bundle do> and <end> lines in app/views/layouts/standard.html.erb. Unless you do this you’ll get errors as soon as you view a page.
b) Copy config/site.yml.tmpl to config/site.yml, customise it as required, and check it in to git. This is important because we need git to upload it to heroku, so it needs to be checked in. You might have to remove the site.yml line from .gitignore to achieve this. There’s no need to customise database.yml, heroku will do this automatically on the server.
c) In the tracks directory, type “heroku create”. This will return a URL and remote git URI, as well as configuring a remote in git called heroku

4) Upload. Type “git push heroku master”. Heroku will compile tracks server side, and hopefully print a success message

5) type “heroku open” and your new site should appear.

6) Optional - add a CNAME record to a personal domain and get heroku to recognise it. See http://docs.heroku.com/custom-domains

This is from memory, and now I’ve written it down it looks more complicated than I intended, but I wanted to recommend Heroku, and give some tips on how to host Tracks there.

Hope it helps,

Gavin.

(1.7) Installation on Eleven2

2009-05-01T11:27:35+00:00

hi,

i am having trouble getting to install tracks on my shared server at eleven2 in an apache environment.
i have never, _ever_ used ror and would really appreciate if you guys could help me out…

i uploaded all the files, created a database, configured config/database.yml and /site.yml, created the app under ruby on rails in cpanel and tried to get it installed via terminal with ‘rake db:migrate RAILS_ENV=production’. which did not work.

‘—trace’ yields the following:

======
user at domain dot com [~/public_html/tools/track]# rake db:migrate RAILS_ENV=production—
trace
(in /home/user/public_html/tools/track)
** Invoke db:migrate (first_time)
** Invoke environment (first_time)
** Execute environment
rake aborted!
undefined method `cache_template_loading=‘ for ActionView::Base:Class
/home/user/public_html/tools/track/config/../vendor/rails/railties/lib/initializer.rb
:530:in `send’
/home/user/public_html/tools/track/config/../vendor/rails/railties/lib/initializer.rb
:530:in `initialize_framework_settings’
/home/user/public_html/tools/track/config/../vendor/rails/railties/lib/initializer.rb
:529:in `each’
/home/user/public_html/tools/track/config/../vendor/rails/railties/lib/initializer.rb
:529:in `initialize_framework_settings’
/home/user/public_html/tools/track/config/../vendor/rails/railties/lib/initializer.rb
:526:in `each’
/home/user/public_html/tools/track/config/../vendor/rails/railties/lib/initializer.rb
:526:in `initialize_framework_settings’
/home/user/public_html/tools/track/config/../vendor/rails/railties/lib/initializer.rb
:154:in `process’
/home/user/public_html/tools/track/config/../vendor/rails/railties/lib/initializer.rb
:112:in `send’
/home/user/public_html/tools/track/config/../vendor/rails/railties/lib/initializer.rb
:112:in `run’
/home/user/public_html/tools/track/config/environment.rb:9
/usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require’
/usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require’
/home/user/public_html/tools/track/vendor/rails/activesupport/lib/active_support/depe
ndencies.rb:153:in `require’
/home/user/public_html/tools/track/vendor/rails/activesupport/lib/active_support/depe
ndencies.rb:521:in `new_constants_in’
/home/user/public_html/tools/track/vendor/rails/activesupport/lib/active_support/depe
ndencies.rb:153:in `require’
/home/user/public_html/tools/track/vendor/rails/railties/lib/tasks/misc.rake:3
/usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:617:in `call’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:617:in `execute’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:612:in `each’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:612:in `execute’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:578:in `invoke_with_call_chain’
/usr/lib/ruby/1.8/monitor.rb:242:in `synchronize’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:571:in `invoke_with_call_chain’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:588:in `invoke_prerequisites’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:585:in `each’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:585:in `invoke_prerequisites’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:577:in `invoke_with_call_chain’
/usr/lib/ruby/1.8/monitor.rb:242:in `synchronize’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:571:in `invoke_with_call_chain’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:564:in `invoke’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2027:in `invoke_task’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2005:in `top_level’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2005:in `each’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2005:in `top_level’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2044:in `standard_exception_handling’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:1999:in `top_level’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:1977:in `run’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2044:in `standard_exception_handling’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:1974:in `run’
/usr/lib/ruby/gems/1.8/gems/rake-0.8.4/bin/rake:31
/usr/bin/rake:19:in `load’
/usr/bin/rake:19
==============================

cheers,

dmd.

No style

2009-05-05T04:08:16+00:00

After installing Tracks on Dreamhost, I get this in both Firefox and IE:

http://www.contriving.net/ftpd/forums/ugly.JPG

How do I fix or troubleshoot this?

Tracks using a lot of memory?

2009-04-29T07:09:51+00:00

I really like Tracks, it’s an awesome app. But on my baby VPS (which has 256mb of RAM), it uses about 90 of those megs. Is that normal? Is there anyway I can pair down that amount? As it is, I need to figure out how I can keep Tracks going without affecting my main site. Which might be upgrade my VPS

I am using Apache 2.2 with Phusion Passenger and MySQL. I’ve got PassengerPoolIdleTime set to 0 (ie, keep the rails processes alive indefinitely). Tracks, version 1.7, is running in production mode.

Installation On Dreamhost

2006-07-31T19:44:25+00:00

There is an installation tutorial linked to on the main page here, but it is woefully out of date. I have done my best to install Tracks on my host (Dreamhost) but am not having any luck. I have created the database and verified that the migrate script was able to create the database tables. I have uploaded the app to my website, creating a subdomain dedicated to it: http://gtd.mydomain.com. When I access tracks via a web browser at that URL, I get a 404. If I try http://gtd.mydomain.com/public/, I get “Rails application failed to start properly.“ I get a 404 when I try /signup. I even tried downloading and compiling the latest version of ruby and updating the scripts here to have the path to that version of ruby (/home/myuser/bin) and still have the same issues.

I’m open to starting again if anyone can provide up to date installation instructions. If not, can anyone give me an idea of some things to check? This application is far, far, too complicated to install. It needs to move in the direction of being an install as simple as wordpress or movable type or something…

I must not understand web hosting

2009-04-22T17:22:25+00:00

I thought I had this concept, but maybe not.

I’m old to computers, GTD, and the web; new to Tracks, which I like a lot.

Mac OS X 10.5.6, btw.

I found Tracks a couple of years ago, but couldn’t grok the install (decidedly not a code geek).

Found a Lifehacker article this week that offered an easy install via BitNami (http://bitnami.org/stack/tracks), which directed me to Morph eXchange.

This “installation” seems to be working fine, so my question is:

Do I need a web host to run Tracks?

Thanks for helping the clueless.

tracks on hostgator howto

2009-03-31T18:01:51+00:00

i finally got the trick, here is how it worked for me:
- ignore the forum post about rails installation
- ignore support staff that only points you to the forum post
- use cpanel/rails to create rails app and webforwarder
- delete rails app template and unpack tracks here
- do some environment magick*
- in cpanel/rails start webapp

*what environment magick is needed?
in config/environment.rb add this line:

Rails::Initializer.run do |config|
  # some hosting might need this (hostgator does)
  config.load_paths += %W( #{RAILS_ROOT}/vendor/plugins ) 

[it might make sense to include this to tracks as i dont think it makes harm to others…]