There are a myriad of use cases for this, but, for me, it came down a Rails API that needed to be communicating solely over SSL and (ultimately) a web app that needs to be doing the same. Getting things functioning over my local server only for them to be upset on staging due to a SSL error is not fun.
Creepiest error message ever. *Wide-Eyed*
Kiip recently completed a migration from EC2 to VPC. VPC exited beta and became generally available in all regions in August, and allows you to provision compute nodes within a virtual network in AWS. For anything more than simple websites, we believe migrating to VPC is something worth doing, or at the very least worth investigating.
Because Amazon VPC is a new service and requires a substantial amount of domain knowledge, this article will first cover a quick intro to the benefits and parts of building a VPC. Specific details about our VPC architecture here at Kiip, tooling we’ve built around it, and our migration process will be covered in future posts.
Pretty sweet outline.
I wrote a while back about how Turbolinks means that document.ready doesn’t function as you’d expect because, technically, no page is being loaded. Specifically, I said:
I had a wonky solution at the time. However, I recently ran into this much simpler solution (at least from our perspective, I’m sure the gem’s creator had a fun time):
add gem ‘jquery-turbolinks’ to your gem folder
add //= require jquery.turbolinks to your application.js file in your assets folder
Just in case anyone else has been wasting time creating their own workarounds or trying to solve jquery ‘bugs’ that don’t exist.