Just a quick shout out for those having a problem with the latest DelayedJob, this is a quick fix!

If you're building ActiveModel-like classes, it's quite useful that you run the ActiveModel Lint tests that's shipped with Rails 3. Unfortunately, if you're using Rspec 2.0, using the Test::Unit version doesn't fly as well.

Our experience so far with rails 3 has been pretty good. Some of the modules and internals of rails were renamed, but so far we haven't experienced anything that changed drastically. Most of the stuff still have some parallelisms.

We're building a very simple app, and we decided to start with Rails3. Here is our stack so far:

1. Rails3
2. HAML
3. Paperclip
4. is_taggable
5. twitter-auth
6. mocha
7. shoulda
8. factory_girl

If ever you want to include staging when using asset packager, just write this initializer

If you're using the auto_migrations plugin to collaborate on a project, you may have stumbled on the problem of having a conflict on the version part of your schema.rb.

*shameless plug*

I created a fork of it that basically prevents this problem / nuisance from happening.

Most of the example or open source code built for rails I see usually use the class name Notifier for their mailer. I was peer-pressured into doing so also, but lately I've been thinking about this convention and stumbled on a possibly better naming.

If you've ever had the setup of using cucumber, autospec, and sunspot SOLR in one your rails applications, chances are you've tried hitting your SOLR test instance just to verify that the whole stack works.

The best thing since sliced bread? (Or maybe sliced host)...

Heroku lets you create a free account and handles everything, from git hosting to mysql data storage, etc.

Git push means cap deploy

Scenario: Grant access to some assets only to premium users

How do we go about doing this in an efficient way?

Prevent direct access to your assets

If you're using NginX, the following configuration would handle this part:

I have been very interested and locked to background processing ever since I've employed it. I have tried Starling, Delayed::Job, beanstalk, ActiveMessaging, ZeroMQ, and RabbitMQ. Here's a quick rundown:

The Giant Central Model

I've been working for over a year at recomed.com, which basically is a social network for doctors that aids people in potentially finding the right doctor for their needs.

Hair Pulling Galore

Have you ever run into the problem in Rails Metal where AJAX Requests just choke? When you try and debug the error response, it would stupidly reply "parseerror".

I ran into this error earlier, and I got to tell you, this is really one puzzling error message.

Basically I have the code in my routes that does this:

Since Rails 2.3 is the only Ruby 1.9 compatible version of rails, and shoulda hasn't yet made the move to support Rails 2.3, I'm gonna play a little waiting game and try and let the guys at thoughtbot update shoulda.

Since I'm slowly (but surely) making the move to ruby 1.9 each day, I discovered that starling doesn't work with ruby 1.9, and most probably, it never will.

The guys at twitter have moved to kestrel for a time now, so I guess that's the best move for me as well. Considering switching to an entirely different queue server with a different protocol will incur too much overhead as of this moment.