Skip to content

Rails: Prefer Devise for Authentication #736

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Rails: Prefer Devise for Authentication #736

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions rails/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -130,6 +130,15 @@ others' Rails work, look in particular for:

[ActiveStorage]: https://guides.rubyonrails.org/active_storage_overview.html

## Authentication

- Prefer [Devise][] over the [authentication generator][], due to its wide
adoption, rich [ecosystem][], and security maintenance.
Comment on lines +135 to +136
Copy link
Contributor

@vburzynski vburzynski May 9, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. Could this be expanded to cover the set of architectural characteristics and project needs which would indicate Devise being a better choice and what set would indicate one should use Clearance?
    • For example, a simple forms-over-data CRUD and simple REST based small Rails app might benefit more from Clearance. Clearance might support architectural characteristics like simplicity, maintainability, agility; as it's a more lightweight solution. It could also cost-less to implement if its feature set covers the needs of the app. Yet if an app is likely to expand beyond what Clearance can offer, the implementation team would need to weigh the cost of replacement or enhancing Clearance.
    • on the other hand, an app with architectural characteristics that prioritize upgradeability, extensibility, configurability, and leverageability/reuse might want to choose Devise. Devise comes with a long list of third party extensions and a larger feature set. It's more commonly used across Rails applications. That large feature set comes with some complexity and challenges, but it's more ubiquitous in the Rails community.
    • so there are tradeoffs to using one or the other.
  2. This guideline might also benefit from creating a "guideline page" to expound on the reasoning (including what's mentioned in the PR description).


[Devise]: https://github.com/heartcombo/devise
[authentication generator]: https://guides.rubyonrails.org/security.html#authentication
[ecosystem]: https://github.com/heartcombo/devise?tab=readme-ov-file#extensions

## How to...

- [Start a New Rails App](./how-to/start_a_new_rails_app.md)
Expand Down