Pundit
Scenic
Pundit | Scenic | |
---|---|---|
25 | 8 | |
8,175 | 3,341 | |
0.3% | 0.6% | |
6.7 | 5.8 | |
about 1 month ago | 25 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.
Scenic
-
Database Views & Rails Active Record: defining new Model classes out of views
To model our Deliverable class, we will need a view. We will use the popular scenic gem, which provides some useful generators for creating views with their respective migrations, and utilities to handle views versioning.
-
Materialised views for serious performance gains
+1 for scenic - https://github.com/scenic-views/scenic
-
Most performant way to build an analytics dashboard from a relational database backend that only stores numeric values, where the data the end-user sees is "categorized" into numeric brackets (e.g. 60-79 = Med, 80-100 = High, etc)
If the data doesn't need to be close to real-time, and if your DB can handle a bit of load, I'd use a "batch" approach. To do this, I'd create a materialized view in your relational DB that you'd then refresh periodically. The easiest way to do this is with the `scenic` gem. Once you've done this, you can simply create a new model and set the `table_name` to the name of the materialized view, and then treat it as a regular model.
- Utilizando views SQL no Ruby on Rails
-
Frameworks for SQL Development in Rails?
I use the scenic gem to manage views which uses raw sql files: https://github.com/scenic-views/scenic
-
Rails application boilerplate for fast MVP development
add scenic
-
Logidze 1.0, postgres-specific alternative to eg paper_trail for recording ActiveRecord change history
TIL about fx gem for storing triggers in schema.rb. That makes me so happy because scenic gem for creating database views is one of my favorites. Postgres is very powerful and it's great to see tools for exposing that through Rails.
What are some alternatives?
CanCanCan - The authorization Gem for Ruby on Rails.
Lol DBA - lol_dba is a small package of rake tasks that scan your application models and displays a list of columns that probably should be indexed. Also, it can generate .sql migration scripts.
rolify - Role management library with resource scoping
PgHero - A performance dashboard for Postgres
Action Policy - Authorization framework for Ruby/Rails applications
SecondBase - Seamless second database integration for Rails.
Devise - Flexible authentication solution for Rails with Warden.
Polo - Polo travels through your database and creates sample snapshots so you can work with real world data in development.
Authority
SchemaPlus - SchemaPlus provides a collection of enhancements and extensions to ActiveRecord
Declarative Authorization - An unmaintained authorization plugin for Rails. Please fork to support current versions of Rails
Ruby PG Extras - Ruby PostgreSQL database performance insights. Locks, index usage, buffer cache hit ratios, vacuum stats and more.