RubyFlow The Ruby and Rails community linklog

×

The Ruby and Rails community linklog

Made a library? Written a blog post? Found a useful tutorial? Share it with the Ruby community here or just enjoy what everyone else has found!

Submit a post

You can use basic HTML markup (e.g. <a>) or Markdown.
Note that your post may be edited to suit the format of the site.

As you are not logged in, you will be
directed via GitHub to signup or sign in

Post Preview

Note: Only the first pargraph is shown on the front page and overly long paragraphs may be broken up.

A lightweight way to handle different validation situations

Say you have an Article model, and it could be either a draft or a published article. The published article needs more validation than the draft. What’s the best way to write this? Rails has a lightly documented, little-known feature that makes these problems really easy to handle.

ActiveRecord count vs length vs size and what will happen if you use it the way you shouldn’t

One of the most common and most cumbersome errors you can make: using length instead of count. You can repeat this multiple times, but you will always find someone who’ll use it the way it shouldn’t be used. Here as a reminder: ActiveRecord count vs length vs size and what will happen if you use it the way you shouldn’t

Ruby & Rails: Making sure rake task won’t slow the site down

If you don’t have multiple cores and/or you have a small VPN, you may end up with a huge slow down of your web app, when rake tasks are executed. This can be a big issue especially when you use something like whenever to perform periodic tasks. Luckily there’s a nice. You can read more about how to use it here: Ruby & Rails: Making sure rake task won’t slow the site down

Write Reliable, Asynchronous Integration Tests With Capybara

Integration tests involving Ruby and JavaScript are fraught with danger. Developers frequently complain of tests which fail erratically. It is possible to write reliable, asynchronous integration tests with Capybara by understanding how Capybara, Ruby, background processes, threads, processes and Capybara drivers such as Selenium, Capybara Webkit, and Poltergeist work, and by following some easy-to-remember guidelines.

Gathering Additional Profile Attributes Using Devise

The fantastic Devise authentication gem asks registering users for just two items: an e-mail address and password. Chances are you’ll want to subsequently gather additional details, such as the user’s name or location, typically done through an account profile management form. In this post I show you how this is accomplished.

Loading older posts