react-on-rails
Pundit
Our great sponsors
react-on-rails | Pundit | |
---|---|---|
9 | 25 | |
5,058 | 8,170 | |
0.6% | 0.7% | |
7.3 | 6.9 | |
1 day 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.
react-on-rails
-
Considering moving from NextJS to Rails
You should take a look at https://github.com/shakacode/react_on_rails. I created that repo back in 2015 and it's still going strong. Popmenu.com uses it and we've got 5,000 restaurant chains on the Rails monolith and huge traffic and transaction volume. Check out the html source of a popmenu site, like https://110grill.com. You'll see react-on-rails in the source.
-
Spent the past week learning Stimulus and Hotwire - you don't need it, you can do the same thing with jQuery
It's me, Justin, the guy the started React on Rails and React on Rails Pro many years ago! I'll be following this thread!
-
Best project setup for Rails+React with "remember me" feature
The problem is I have no idea how to implement the "remember me" feature in that gem without just making the tokens not refresh for a very long time (I think that would be a security concern). So then I looked more into react_on_rails to just use sessions with Devise as a normal rails app, but I don't know if I'll be able to deploy that on AWS because of the changes I have to do to the webpacker/webpack config to allow for a better folder structure. I've never done that so I don't know if there may be any issues.
-
Frontend based access control?
I have a production level Ruby on Rails app that is slowly transitioning from pure Rails with JS sprinkles to a Rails backend and React frontend kind of situation using React on Rails.
- How to create a project with both .erb and react? Do I use webpack=react?
-
Does anyone know a way to make a React with Rails application SEO friendly?
https://github.com/shakacode/react_on_rails - It was last updated 2 months ago & can do prerendering. I'm not sure why more people aren't suggesting this.
-
React Frontend vs Hotwire
https://github.com/shakacode/react_on_rails use this instead. It's maintained and preferred nowadays
- Hotwire: the new evolution of Turbolinks from Basecamp
-
26 most popular Ruby/Rails repositories on GitHub in July-August 2020
React on Rails is an integration of React + Webpack + Rails + rails/webpacker including server-side rendering of React, enabling a better developer experience and faster client performance. 4,558 stars by now
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?
react-rails - Integrate React.js with Rails views and controllers, the asset pipeline, or webpacker.
CanCanCan - The authorization Gem for Ruby on Rails.
Ruby on Rails - Ruby on Rails
rolify - Role management library with resource scoping
Roda - Routing Tree Web Toolkit
Action Policy - Authorization framework for Ruby/Rails applications
Sinatra - Classy web-development dressed in a DSL (official / canonical repo)
Devise - Flexible authentication solution for Rails with Warden.
backbone-react-component - A bit of nifty glue that automatically plugs your Backbone models and collections into your React components, on the browser and server
Authority
react-d3-library - Open source library for using D3 in React
Declarative Authorization - An unmaintained authorization plugin for Rails. Please fork to support current versions of Rails