revise_auth
Sorcery
| revise_auth | Sorcery | |
|---|---|---|
| 1 | 10 | |
| 327 | 1,413 | |
| - | 0.8% | |
| 8.2 | 5.8 | |
| 4 days 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.
revise_auth
Sorcery
-
Everything was going great until I installed Devise!
I have been using devise for a while and it has consistently given me issues. I have wistfully been staring at sorcery for a while now but cant justify the switch since devise is already in the project.
- What is used for authentication in Rails nowadays?
-
Build a password authentication feature with Sorcery gem.
I made a 8 minutes video tutorial (following the wiki: https://github.com/Sorcery/sorcery/wiki/Simple-Password-Authentication) to introduce how to build a simple password authentication feature with Sorcery. With some minor modification to please Turbo.
-
Authentication with Sorcery, RSpec, and Rails 7: Building a simple Rails CMS - Part 1
We'll be installing Sorcery based off this tutorial in their wiki. I'm modifying a little bit since we are creating something different, but also because their tutorial is a bit outdated since it is based off an older version of Rails.
- Webpacker Retired
- What are your top useful gems?
-
A November of WTFs
But does it have to be so soon? There are other areas where I'm just as ignorant as I was about the inner workings of authentication (see "the database" below), and in these areas there's not a gem that can automatically solve the problem for me—which is what I've ended up doing for authentication in my own project: even though I could build authentication from scratch, instead I'm using an authentication gem because the effect is exactly the same, but with less code in my app for me to maintain. (Rather than Devise, I've chosen the more lightweight alternative Sorcery. It's simple enough that I can still understand and control the authentication flow, while also providing enough conveniences that I don't have to write out implementation details from scratch.)
-
Why there is no simple default auth in Rails?
Also Sorcery is, despite its name, a little less magic than Devise.
-
Easy has_secure_password API authentication
sorcery
What are some alternatives?
GraphBoard - Rails 7 federated microservices, Apollo Gateway on Typescript, Golang video streaming. read readme.
Devise - Flexible authentication solution for Rails with Warden.
Clearance - Rails authentication with email & password.
Karafka - Ruby and Rails efficient multithreaded Kafka processing framework
OmniAuth - OmniAuth is a flexible authentication system utilizing Rack middleware.
devise_masquerade - Extension for devise, enable login as functionality. Add link to the masquerade_path(resource) and use it.
Authlogic - A simple ruby authentication solution.
JWT - A ruby implementation of the RFC 7519 OAuth JSON Web Token (JWT) standard.
Knock - Seamless JWT authentication for Rails API
Doorkeeper - Doorkeeper is an OAuth 2 provider for Ruby on Rails / Grape.
warden - General Rack Authentication Framework