Ahoy
Pundit
Our great sponsors
Ahoy | Pundit | |
---|---|---|
15 | 25 | |
4,078 | 8,164 | |
- | 0.6% | |
7.5 | 6.9 | |
12 days ago | 27 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.
Ahoy
-
Ahoy Captain: a full-featured, mountable analytics dashboard
A full-featured, mountable analytics dashboard for your Rails app, which is a blatant rip-off of heavily inspired by Plausible Analytics, powered by Ahoy. Open source, though lots of changing parts: https://github.com/joshmn/ahoy_captain
-
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.
For logging which functions were used you can use ahoy
-
How would you build an audit log in Rails for a high-throughput API?
Ahoy may be worth a try https://github.com/ankane/ahoy
- Want to keep track of URL visits, what's the simplest way to do achieve this?
-
Italian watchdog bans use of Google Analytics
I've slowly started ripping Google Analytics out of my Rails projects and replacing it with https://github.com/ankane/ahoy.
It's so much better! I can just use SQL to see what's going in and not get overwhelmed with 100's of visualizations and complicated dashboards.
-
Need some good documentation on implementation or tutorial video for AHOY gem
it's just a database table, so yeah, a migration is fine: https://github.com/ankane/ahoy/issues/461
-
Make Ahoy Queries faster?
I'm using the ahoy gem for analytics on my website (https://github.com/ankane/ahoy).
-
Cookie-based tracking is dead
I did server-side tracking test in a rails app, where I implemented a tracking gem called ahoy and blazer for visualization. It is very easy to set up, but a bit hard to use. Blazer can do a very basic visualization of the data if you know your SQL queries.
-
How would you build/record/store analytics data ;
https://github.com/ankane/ahoy The ahoy gem is pretty useful for this. Data model is pretty simple, it will track unique user sessions and metrics you specify will be associated with these sessions. The gem also parses the user agent, so it will indicate whether a session was on mobile, desktop or tablet.
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.
What are some alternatives?
Impressionist - Rails Plugin that tracks impressions and page views
CanCanCan - The authorization Gem for Ruby on Rails.
Legato - Google Analytics Reporting API Client for Ruby
rolify - Role management library with resource scoping
active_analytics - First-party, privacy-focused traffic analytics for Ruby on Rails applications.
Action Policy - Authorization framework for Ruby/Rails applications
Staccato - Ruby library to perform server-side tracking into the official Google Analytics Measurement Protocol
Devise - Flexible authentication solution for Rails with Warden.
Gabba - Simple way to send server-side notifications to Google Analytics
Authority
Analytical
Declarative Authorization - An unmaintained authorization plugin for Rails. Please fork to support current versions of Rails