1.3.4 was a quick follow up to 1.3.3 to make rack_protection key work again for the few people that were using it. 1.3.5 hopefully fixes some nagging issues. The first is around frozen strings in Ruby 3.4. A couple spots were using| The Friday Deploy
Join me on a journey of solving the dilemma of warming up a "cold" cache cluster via feature flags without causing chaos.| The Friday Deploy
Learn how feature flags via Flipper can instantly enable/disable web forms, protecting your forms from bots and spammers.| The Friday Deploy
Releasing code behind feature flags when much of the related functionality is incomplete can sometimes require creative solutions. For example, if some new functionality requires a new column with a default value, how can we handle the scenario where the database’s default value should be different after the| The Friday Deploy
Flipper is sporting a snazzy new CLI and some testing improvements, among a handful of small improvements.| The Friday Deploy
While feature flags are great for managing the roll out of customer-facing features, they're capable of so much more. We use feature flags internally in conjunction with performance and analytics tools.| The Friday Deploy
Dearest feature flagger, I come today bearing good news. A new year and a new release! Only a patch, but it's got some nice bug fixes and other treats. Redis Connection Pools Let's lead with the 🔥. I'm happy to report that the redis and redis cache adapters now work with| The Friday Deploy
Dearest feature flagger, I just pushed out Flipper 1.3.1. Here are the deets: #862 - Removed redundant delete of feature gate in ActiveRecord adapter. #832 - Respect Rails defaults in an initializer by delaying loading ActiveRecord adapter until framework is loaded. #869 - Address soft deprecation of| The Friday Deploy
When we started billing for Flipper Cloud, we did what everyone else in the space was doing – per seat pricing. $20 per seat each month felt like plenty. As time has passed this choice has increasingly bothered me. The past few months I've been thinking about what type of billing| The Friday Deploy
You know what they say... there are 2 hard things in computer science: cache invalidation, naming things and off-by-1 errors. That's true for feature flags as well. You don't always get the name quite right before the feature flag gets used in production. But once the flag is in use| The Friday Deploy
You might not have noticed it, but Flipper 1.3.0 (released in April) enabled telemetry by default for everyone using Cloud. This means for the past month or two (whenever you upgraded), we've been rolling up some useful metrics and shipping them to Cloud. Nothing personal is in the| The Friday Deploy
A new release of your favorite flipping gem is out. Explicit actor limits, UI updates, easier adapter wrapper, cloud telemetry and more…| The Friday Deploy
A few weeks ago I switched Box Out and Flipper Cloud to AppSignal. I've been loving it so far! The only snag I hit was cost for Cloud (not for Box Out). Previously, Cloud was using New Relic and paying around $180/mo. After a few weeks on AppSignal I| The Friday Deploy
With Flipper's new telemetry, we can see when a flag hasn't been requested in production (or any environment for that matter) for a long enough window that it's safe to remove. That creates a lot of peace of mind when cleaning up stale flags.| The Friday Deploy
Adding feature flags is easy but deleting them requires care and safety. We even mess it up. Before you delete a flag, you have to remove it from the code. If you don't remove it from the code, deleting a flag is the same as disabling it.| The Friday Deploy