#1: Devise Part 1: Setting Up Devise With Rails 7 And React
- ruby
- ruby-on-rails
- devise
In part one of this six part series on Devise and Ruby on Rails, we demonstrate setting up Devise for Rails 7 with a basic sign up and login flow.
A personal blog on all things of interest.
Written by Dennis O'Keeffe
In part one of this six part series on Devise and Ruby on Rails, we demonstrate setting up Devise for Rails 7 with a basic sign up and login flow.
In part two of our Devise series, we look at how we can replace the default cookie session store with Redis.
In part three of the series, we walk through how to add TailwindCSS to a Rails 7 project and spruce up our sign in page.
In part four, we add in a separate Next.js project into the mix and demonstrate how to organize authentication for our main Rails API.
In part five, we set up the OmniAuth configuration for Devise to demonstrate login using GitHub.
In part six, we enforce the usage of reCAPTCHA v2 to prevent signing up or logging in without passing the reCAPTCHA verification.
For this part, we look at setting up some helpers for us to log users in when writing controller tests.
This post looks at how we outline required policies in order to fulfill requests in Ruby on Rails using the Pundit gem.
In part nine, we take a look at how we can set up our API endpoints to return a 401 response if a user is not signed in instead of the default 302 redirect to the login page.
1,200+ PEOPLE ALREADY JOINED ❤️️
No spam. We only send you relevant content.