Our latest feature saves you a click or two — and you're going to love it. You probably already know that Honeybadger can let you know which users were impacted by an error in your Rails application. By using the context feature you can send custom data, such as a user id and a user email address, along with the other application data that's automatically sent with each error report. I use this all the time to quickly email people to let them know that the error they just encountered at my site has already been fixed. They love that. :)
Today we're announcing the launch of a fun feature: In-browser notifications. Once enabled on the Notifications tab of the Project Settings page, you'll get a popup notification in the corner of the browser window when one of the events occurs that you've selected to be alerted about (like an error occurring, or a comment being added). As an added bonus, you can also choose to have a popup window appear on your desktop. The combination of Pusher and pNotify made this easy to implement -- here's how I did it.
LessAccounting has been in production since 2007 and it was started in Ruby 1.8.6 and Rails 2. Yeah, it’s been around for a while.
We’re excited to announce our partnership with Cloud 66 - a service to provision, deploy and scale Ruby apps on your own servers on any cloud.
If there ever was a task that seemed straightforward from the outside, but then turned out to be really complicated when you got into it, a multi-step form is it.
One of the things that makes working with Rails so nice is that for any common programming need---authorization, site administration, ecommerce, you name it---someone smarter than you has likely coded up the solution for your problem and packaged it up in the form of a gem.
Testing controllers in Rails engines with RSpec requires you to jump through some hoops. If memory serves, it was slightly trickier in Rails 3 than it is now in Rails 4. Fortunately the fix is pretty easy, if not obvious.
Vim is objectively the best code editor there is. [Editor's note: Opinions are those of the author. Honeybadger remains neutral in the vim/emacs/sublime holy war]
Here at Honeybadger we're big fans of eating our own dog food. We were all contractors when we started Honeybadger, and still use our own software regularly to monitor our personal projects. One of the main benefits of this is that it's not difficult to see the product from our customer's perspectives; we are the customer!
One of the most important things to know about Rails 4.1 is that even the beta version is stable enough for some companies to use it in production. For example,Basecamp began Rails 4.1 beta1. Other important features from the release notes include the Spring application preloader, changes to config/secrets.yml, Action Pack variants, and Action Mailer previews. You can find the full list of changes by reviewing the list of commits in the GitHub repository for Rails.
If you're like most Rails developers I know (including myself), you're probably used to writing "unit" tests in RSpec that load up the whole Rails framework before each test, which takes a few seconds to do, even if you're only testing one tiny thing.
One of the hairiest challenges of working with some legacy applications is that the code wasn't written to be testable. So writing meaningful tests is difficult or impossible.
If you've been using the Unix/Linux command line for any length of time, you're certainly familiar with time-saving techniques like tab completion and reverse-i-search. Chances are you use these darling keystroke-savers daily.
Today is a big day for us. It’s the first day of our OFFICIAL partnership with the fine folks over at PagerDuty.
Uptime and performance monitoring for ruby and rails applications
A screed + a screencast showing you how to host your own gems