Friday, September 12, 2008

Rubyforge gem problem

Problem:

starting the server and you get:
 can't activate rubyforge (= 0.4.5), already activated rubyforge-1.0.0] (Gem::Exception)

Solution:
remove old versions of rubyforge gem
jorrel@helen ~ $ sudo gem uninstall rubyforge

Select gem to uninstall:
1. rubyforge-0.4.4
2. rubyforge-0.4.5
3. rubyforge-1.0.0
4. All versions
> 1
Successfully uninstalled rubyforge-0.4.4
jorrel@helen ~ $ sudo gem uninstall rubyforge

Select gem to uninstall:
1. rubyforge-0.4.5
2. rubyforge-1.0.0
3. All versions
> 1
Successfully uninstalled rubyforge-0.4.5
jorrel@helen ~ $ gem list | grep rubyforge
rubyforge (1.0.0)

Tuesday, June 17, 2008

Undo uncommitted changes in git

It seems that 'git revert' does not work the way that 'svn revert' does (reverting all uncommitted changes). I don't know if this is the proper way, but I 'reverted' my changes using 'git stash':


git stash
git stash clear

Update:

git reset --hard

Monday, April 28, 2008

Ubuntu Hardy + Firefox + Firebug

The old firebug is not working for firefox 3 beta 5 in Ubuntu Hardy; and so firebug 1.1 from the official site.

Solution: get the 'firebug' package from apt. :)

Tuesday, April 22, 2008

mod_rails + edge rails

Based on a recent conversation at phusion passenger google group, there is a bug wherein mod_rails fails to start its spawner for an application that uses edge rails.

Basically, you'll get this error (complaining about a failed 'to_constant_name' somewhere):

  Framework that failed to load:
Vendor directory: /path/to/vendor/rails
Error message:
Anonymous modules have no name to be referenced by
Exception class:
ArgumentError

More info about the bug can be found in the bug report filed by hongli


update: This seems to be fixed in edge rails + git passenger (though I havn't tried yet), as hongli's comment below says.

Monday, April 14, 2008

mod_rails + rails 2.0

I you encounter a "500 Internal Server Error" after setting up mod_rails in a recent (rails 2.0) application, you need to delete 'public/.htaccess'.

Monday, January 28, 2008

Detecting the googlebot

Detecting the googlebot as your site's visitor is easy by just checking user agent. Googlebot uses this user agent:
Googlebot/2.1 (+http://www.googlebot.com/bot.html)

And in the app, we can just check:
request.user_agent =~ /googlebot/i

Friday, January 25, 2008

Planned Music Purchases

Purchase albums:

and/or

once available and not too lazy to go to the mall.