hat happens when you have a bug in your API, and you need to fix it for some clients (the updated ones), but not for others? This screencast illustrates a strategy for adjusting an API's behavior for specific clients. We'll be using the Ruby on Rails framework emitting JSON to demonstrate this important web and API concept.
Whether you are building a prototype or a business critical product, Heroku makes it easy to deploy and scale web applications. If you’ve never run a production web application before this might sound intimidating, but don’t worry—we’re going to use Heroku, a platform that makes deploying apps incredibly easy. But first we have a little preparation to do.
In a previous screencast we set up a simple Rails web service for todos and deployed it to production. But right now there's no authorization on it, which means anyone can come along and modify our data. In this screencast, we’ll use the Doorkeeper gem makes it easy to add authentication to Rails APIs using the OAuth 2 standard.
In a previous screencasts, we built out a simple but full-featured web service. We have several tables of related data, validation, default values, and authorization. This is great, but it’s also starting to get complex enough that we might break something! Luckily, Rails’ testing support is second-to-none. In this screencast, we'll learn how to set up automated testing for our Rails web service.
Integration tests describe a server’s overall behavior and capabilities. These tests can quickly expose failing systems, help developers isolate bugs and make server-sized refactors safer. In this screencast, we’ll show you how to configure the Chai HTTP extension with the existing test suite for the Chattrbox app.