rack

I recently helped debug Grape#1880, an issue a developer had with HTTP headers in Grape and Rack. It wasn’t immediately obvious.

I’ve recorded a screencast during the Anatomy of a Ruby Gem meetup in New York. It’s a deep dive into Grape internals.

I’ve seen two common API versioning strategies in the wild. The first is to use a single API version and gradually deprecate methods. This usually means introducing new API rout...

I’m very excited to Release Grape 0.4.0 today. Again, thanks to the 10 (!) contributors to this release.

Grape’s after blocks don’t allow you to modify response text or status code [#200]. So how can you wrap an API response?

One of the frequently requested features in Grape is to automatically reload code changes, much like Rails does (#131). This is actually pretty difficult to implement and requir...

Expanding from my previous post on a Grape API mounted on RACK.

tl;dr – the source is here

We’re using Grape in our Rails app on Heroku, which comes with New Relic instrumentation out-of-the-box. Let’s get the Grape API route details to show in New Relic as well.