It’s been two months since the first beta release of Rails 5.2, and we’ve spent the time since to improve, polish, and tweak the release in all sorts of lovely ways for this first release candidate.
Our headline feature, the new Active Storage framework, has been expanded with deeper content-type identification, as well as a ton of other improvements. It also had a few extra months of battle-testing in production at both Basecamp and elsewhere. It’s a very solid framework out the box.
During the beta, we’ve also managed to squeeze in a few additional improvements. Like super-fast fixture loading, custom error handling on Active Job discarding, and call-site logging for Active Record queries in development. The wheels never stop turning!
So we’re getting close. Basecamp and lots of other shops have already been running the Rails 5.2 beta in production for months.
Our target for either the next release candidate or final, depending on the severity of issues that may pop up, is before the end of February.
But since this is a release candidate, we’ll already now move
rails/5-2-stable, and thus free up
rails/master to target Rails 6.0 development.
Thanks again to everyone who continue to pour their love and support into Ruby on Rails!
Recap of the highlights of Rails 5.2 from the beta announcement
It’s been too hard to deal with file uploads in Rails for too long. Sure, there’s been a lot of fine plugins available, but it was overdue that we incorporated something right into the framework. So now we have!
With the new Active Storage framework in Rails 5.2, we’ve solved for the modern approach of uploading files straight to the cloud. Out of the box, there’s support for Amazon’s S3, Google’s Cloud Storage, and Microsoft Azure Cloud File Storage.
If you’re dealing with images, you can create variants on the fly. If you’re dealing with videos or PDFs, you can create previews on the fly. And regardless of the type, you can analyze uploads for metadata extraction asynchronously.
Active Storage was extracted from Basecamp 3 by George Claghorn and yours truly. So not only is the framework already used in production, it was born from production. There’s that Extraction Design guarantee stamp alright!
Speaking of extractions, Jeremy Daer has untangled the long jungle twine of hacks we were using at Basecamp to employ Redis for general partial, fragment, and other Rails caching jobs. There’s a sparkling new Redis Cache Store that incorporates all those years of veteran hacks into a cohesive unit that anyone can use.
This new Redis Cache Store supports Redis::Distributed, for Memcached-like sharding across Redises. It’s fault tolerant, so will treat failures like misses, rather than kill the request with an exception. It even supports distributed MGETs for that full partial collection caching goodness.
This comes together with a massive leap forward for cache efficiency with key recycling and compression both available by default. For Basecamp, it meant improving the cache lifetime by two orders of magnitude! We went from having caches trashed in as little as a day to having caches last for months. If you’re using partial caching and the nesting doll strategy, your cache lifetime will improve dramatically between these two changes.
On the topic of performance, Rails now ships with Bootsnap in the default
Gemfile, created by our friends at Shopify. It generally reduces application boot times by over 50%.
Rails has always been in the forefront of making your web applications more secure, leading the way with built-in CSRF and XSS protection and we’ve enhanced that further in Rails 5.2 with the addition of a new DSL that allows you to configure a Content Security Policy for your application. You can configure a global default policy and then override it on a per-resource basis and even use lambdas to inject per-request values into the header such as account subdomains in a multi-tenant application.
But it’s not all just new starry-eyed wonders. In Rails 5.1, we added encrypted secrets. These secrets were like the old secrets but, uhm, more secret, because, you know, ENCRYPTION! Confusing? Yes. Why would you want secrets that weren’t really secret? Well, you don’t.
In Rails 5.2, we’ve rectified the mess by deprecating the two different kinds of secrets and introduced a new shared concept called Credentials. Credentials, like AWS access keys and other forms of logins and passwords, were the dominant use case for secrets, so why not just call a spade a spade. So spade it is!
Credentials are always encrypted. This means they’re safe to check into revision control, as long as you keep the key out of it. That means atomic deploys, no need to mess with a flurry of environment variables, and other benefits of having all credentials that the app needs in one place, safe and secure.
In addition, we’ve opened up the API underlying Credentials, so you can easily deal with other encrypted configurations, keys, and files.