@Deprecated

Given that I have finally decided to blog more often now, I’ve created a new blog to be able to do things my way, the TechBot.

All posts and comments placed on here have already been moved so nothing is lost, let’s move on and keep on improving!

Handling various rubies at the same time in your machine with RVM – Ruby Version Manager

This post has moved to my new blog, check it out.

This blog is being terminated.

Full text search in in Rails with Sunspot and Solr

This post has moved to my new block, check it out!

This blog is being terminated :)

Deployment Recipes – Deploying, monitoring and securing your Rails application to a clean Ubuntu 10.04 install using Nginx and Unicorn

This post has moved to my new blog, check it out!

This blog is being terminated :)

Asynchronous email deliveries using Resque and resque_action_mailer_backend

The Rails 3 Way

Check the GitHub repo here and a sample application using it here.

If you have ever sent emails using ActionMailer during a user request you probably noticed that if the email sending fails or takes too long your user might not be really happy with the speed of your application. Making the email sending process an asynchronous one is usually the simplest solution for this problem and there are plenty of tools to do that like ar_mailer, that stores emails in your database and then uses a specific daemon to send them.

ar_mailer and other solutions are quite enough for most of your problems but what if you’re already using Resque to run your asynchronous jobs? Why bother using yet another daemon to do the email sending jobs with all the hassle of managing if you can use your current Resque setup to do it?

With this in mind I sat a bit and wrote this simple gem that lets you do exactly that, send your emails asynchronously using a Resque worker and without changing a single line of your email sending code. Following the same philosophy of ar_mailer, the resque_action_mailer_backend doesn’t require you to call fancy methods on your mailers, you just keep them as they are now and instead of changing them you just change the delivery method to :resque, like this (in a environment file, like “development.rb”):

config.action_mailer.delivery_method = :resque

The gem uses your ActionMailer::Base.smtp_settings configuration to deliver the emails, so you don’t have to change anything in there, just be sure that the SMTP credentials are correct so the worker can deliver emails without issues. The default queue name is “:headbanger_resque_mailer”, but you can change it to whatever you’d like to with this code:

Headbanger::ResqueMailer.queue = :your_email_queue

This single line of code changed will now make all your emails be queued to Resque and they’ll be sent as soon as a worker is available for it. Now you only have to tell your rails application to load the resque_action_mailer_backend gem (in your environment.rb):

config.gem "resque_action_mailer_backend"

You can check a some hints on using this setup at this sample project.

And you’re ready to start sending emails asynchronously using your resque workers!

Enjoy!

If you’re cleaning up your user’s input in your views you’re doing it wrong

This post has been moved to my new blog, check it out!

This blog is being terminated :)

Building your own ActiveRecord validation macros with validates_each

This post has been moved to my new blog, check it out!

This blog is being terminated :)

Setting a far future expires header for your Rails app static assets in your Nginx server

This post has been moved to my new blog, check it out!

This blog is being terminated :)

Accessing the current request object on your mailer templates to generate links

This post has been moved to my new blog, check it out!

This blog is being terminated :)

Why I am not using Masochism for my master-slave setups and why monkey-patching isn’t the only solution

This post has been moved to my new blog, check it out!

This blog is being terminated :)