Pundit
Lograge
Our great sponsors
Pundit | Lograge | |
---|---|---|
25 | 7 | |
8,170 | 3,398 | |
0.7% | - | |
6.9 | 5.0 | |
28 days ago | 28 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.
Lograge
-
Manage Your Ruby Logs Like a Pro
You can choose from a number of third-party logging libraries, including Logging — based on Java's log4j library — and Lograge. Lograge is a feature-rich logging library meant to simplify the often messy and verbose Rails logs characteristic of the default application logger.
- Best rails tools to automatically handle logging of things like all a user's actions, or changes to a record in a module - primarily for audit purposes.
-
What are your top useful gems?
Also a big fan of Lograge, because I just can't stand Rails default logs.
-
Rails application boilerplate for fast MVP development
add lograge
-
Searchable logs with Filebeat and Elastic Stack
To output rails logs into JSON format, we are using lograge gem once you add it in Gemfile and bundle install it will be available to use in you application.
-
Logging in Ruby with Logger and Lograge
There are plenty of options when it comes to picking up a 3rd-party logging framework. The most popular of these is Lograge. Let's take a look at it!
-
Just curious : why is Rails default logging so verbose ?
Check out https://github.com/roidrage/lograge for some settings that work nicely for us in production
What are some alternatives?
CanCanCan - The authorization Gem for Ruby on Rails.
Semantic Logger - Semantic Logger is a feature rich logging framework, and replacement for existing Ruby & Rails loggers.
rolify - Role management library with resource scoping
Fluentd - Fluentd: Unified Logging Layer (project under CNCF)
Action Policy - Authorization framework for Ruby/Rails applications
LogStashLogger - Ruby logger that writes logstash events
Devise - Flexible authentication solution for Rails with Warden.
Log4r - Log4r is a comprehensive and flexible logging library for use in Ruby programs. It features a heirarchical logging system of any number of levels, custom level names, multiple output destinations per log event, custom formatting, and more.
Authority
Logging - A flexible logging library for use in Ruby programs based on the design of Java's log4j library.
Declarative Authorization - An unmaintained authorization plugin for Rails. Please fork to support current versions of Rails
Sidekiq - Simple, efficient background processing for Ruby