Pundit
flipper
Our great sponsors
Pundit | flipper | |
---|---|---|
25 | 10 | |
8,170 | 3,560 | |
0.7% | 1.5% | |
6.9 | 9.6 | |
about 1 month ago | 6 days ago | |
Ruby | Ruby | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Pundit
-
A guide to Auth & Access Control in web apps š
https://github.com/varvet/pundit Popular open-source Ruby library focused around the notion of policies, giving you the freedom to implement your own approach based on that.
-
Pundit VS Action Policy - a user suggested alternative
2 projects | 2 Jul 2023
-
Launch HN: Infield (YC W20) ā Safer, faster dependency upgrades
Can you expand a little? Here's some technical background on what we're doing:
We have our own database of every version of every rubygems package alongside its runtime dependencies (like you see at https://rubygems.org/gems/pundit).
Then we parse your Gemfile and Gemfile.lock. We use the Gemfile to figure out gem group and pinned requirements (we run turn your Gemfile into a ruby AST since Gemfiles can be arbitrary ruby code; we use bundler's APIs to parse your Gemfile.lock). This gives us all of the dependencies your rely on.
Then we let you choose one or more package that you want to upgrade and the version you want to target (let's say Rails 7.0.4.3).
Now we have [your dependencies and their current versions], [target rails version], [all of the runtime dependency constraints of these gems]. We run this through a dependency resolution algorithm (pubgrub). If it resolves then you're good to upgrade to that version of Rails without changing anything.
If this fails to resolve, it's because one or more of your current dependencies has a runtime restriction on rails (or another indirect gem being pulled in by the new rails version). This is where the optimization part comes in. The problem becomes "what is the optimal set of versions of all your dependencies that would resolve with the next version of Rails". Currently we solve for this set trying to optimize for the fewest upgrades. As our dataset of breaking changes gets better we'll change that to optimizing for the "lowest effort".
Happy to elaborate.
-
Authentication, Roles, and Authorization... oh my.
For authorization, I'm going back and forth with Pundit and CanCanCan
-
Protect your GraphQL data with resource_policy
Expressing authorization rules can be a bit challenging with the use of other authorization gems, such as pundit or cancancan. The resource_policy gem provides a more concise and expressive policy definition that uses a simple block-based syntax that makes it easy to understand and write authorization rules for each attribute.
-
Default to Deny for More Secure Apps
As an example of how to default to deny, consider a Ruby on Rails app (as we tend to do). The primary way a user interacts with the app is through API endpoints powered by controllers. We use Pundit, a popular authorization library for Rails, to manage user permissions.
-
Permissions (access control) in web apps
https://github.com/varvet/pundit Popular open-source Ruby library focused around the notion of policies, giving you the freedom to implement your own approach based on that.
-
YAGNI exceptions
PS If you do mobile / web work (or something else with "detached" UI), I find that declarative access control rules are far superior to imperative ones, because they can be serialized and shipped over the wire. For example, backend running cancancan can be easily send the same rules to casl on the frontend, while if you used something like pundit to secure your backend, you either end up re-implementing it in the frontend, or sending ton of "canEdit" flags with every record.
-
Best practice for displaying info to different user roles?
You can use a combination of an authorization gem (https://github.com/varvet/pundit) and decorators (https://www.rubyguides.com/2018/04/decorator-pattern-in-ruby/) if you want to extend functionality based on their roles.
-
Concerns about authorization when going in production
Use Action Policy or Pundit, and write tests for your policies. Authz is worth testing with near complete coverage.
flipper
- Ask HN: How did you build feature flags?
-
Feature flags in Rails: How to roll out and manage your features like a pro
Thatās it! You now have a fully configured feature flagging system in your Rails app. Notice we didnāt cover some more advanced features that Flipper offers, including enabling features for a user group or individual users. For that, check out Flipper on Github. We also didnāt cover feature flagging frontend features in this post - if that becomes a requirement we could easily create an endpoint that uses the FeaturesRepo and sends enabled features to the frontend to toggle. If you learned something new consider following me here - Iāll be putting out more content on Ruby on Rails and software development as I work on Firecode.io. Preparing for a coding interview? Check out Firecode.io.
-
How do you release experimental features to early adopters?
I think you are calling it Runtime Controls: https://github.com/jnunemaker/flipper/issues/162
-
Add Feature Flags in Ruby on Rails with Flipper
Flipper is a gem that makes feature flags and different ways to toggle them available in Rails. It is highly modular. Apart from the main gem, you'll also have to pick a storage adapter ā but more on that later. Let's use the ActiveRecord adapter for now.
-
What Feature Toggle/Flag service are you using?
Since Honeybadger is a Ruby shop, we use the flipper gem.
-
Keeping the Stakes Low while Breaking Production
The next step came about when I learned more about our use of Flipper; a Ruby gem for dynamically toggling on and off features. I didnāt know when the feature would roll out, but I wanted control over the feature. I also wanted admins of other Forems to have control as well. This was trivial with Flipper. Once I deployed the code, Foremās got the original behavior unless they turned āflippedā on the feature.
- Flags vs. Gates
-
Rails application boilerplate for fast MVP development
flipper with Flipper UI to enable flag management
-
Show Rails: Feature Flagging Gem - Lightning
What advantages does your gem have over Flipper?
What are some alternatives?
CanCanCan - The authorization Gem for Ruby on Rails.
Flipflop your features - Flipflop lets you declare and manage feature flags in your Rails application.
rolify - Role management library with resource scoping
Motorhead - A Rails Engine framework that helps safe and rapid feature prototyping
Action Policy - Authorization framework for Ruby/Rails applications
Abstract Feature Branch - abstract_feature_branch is a Ruby gem that provides a variation on the Branch by Abstraction Pattern by Paul Hammant and the Feature Toggles Pattern by Martin Fowler (aka Feature Flags) to enable Continuous Integration and Trunk-Based Development.
Devise - Flexible authentication solution for Rails with Warden.
Ahoy - Simple, powerful, first-party analytics for Rails
Authority
flagsmith - Open Source Feature Flagging and Remote Config Service. Host on-prem or use our hosted version at https://flagsmith.com/
Declarative Authorization - An unmaintained authorization plugin for Rails. Please fork to support current versions of Rails
i18n-tasks - Manage translation and localization with static analysis, for Ruby i18n