Uploaded October 2022 | Updated September 2026, 3 weeks ago
If you have an application where you want to differentiate between your users and personalize their experience, you need a way for them to identify themselves.
Although there is change and innovation occurring in the web authentication space, the most common method of browser authentication is still for a user to sign up for an account with a username and password. They can then log in and create a session with an encrypted cookie that allows their identity to be persisted over time beyond the stateless request-response cycle of a page load.
In this video we talk about the upcoming authentication epic for our NerdDice.com web application. We evaluate alternatives (including rolling our own auth) using the Ruby Toolbox and then decide on the Devise gem.
There are risks associated with choosing Devise. As-of the creation of this video in October 2022, there hasn't been a commit to the main branch of Devise in over three months or a gem release in almost a year. And the current version doesn't work with Turbo or Rails 7 out-of-the-box at all and will need to be patched.
Still, it's likely the lowest amount of effort for the most value in return, and we'll roll the dice on it. (Pun intended.)
This video covers:
00:00:12 Introduction
00:00:59 Overview of the epic's GitHub issue and sub-tasks
00:03:42 Evaluate alternatives using the Ruby Toolbox
00:06:31 Review Devise on RubyGems and GitHub, risk of not receiving recent updates and not working with Turbo
00:09:41 Discussion of using UUID as primary key for User model instead of BigInt
00:11:08 Note on testing approach for this epic and need for browser driven system tests
00:12:43 Overview of the sub-tasks
#ruby #rails7 #rails #rubyonrails #rubygems #codecast #screencast #github #opensource #minitest #TDD #agile #NerdDice #DnD #roleplaying #softwaredevelopment #learntocode #tailwind #postgresql #rubocop #bundler #gemfile #rubytoolbox #devise
This video is CC0 - No rights reserved. (YouTube doesn't allow this option when publishing.) All code is released under the UNLICENSE. Stateless Code denies the concept of "intellectual property". Copying is not stealing.
If you have an application where you want to differentiate between your users and personalize their experience, you need a way for them to identify themselves.
Although there is change and innovation occurring in the web authentication space, the most common method of browser authentication is still for a user to sign up for an account with a username and password. They can then log in and create a session with an encrypted cookie that allows their identity to be persisted over time beyond the stateless request-response cycle of a page load.
In this video we talk about the upcoming authentication epic for our NerdDice.com web application. We evaluate alternatives (including rolling our own auth) using the Ruby Toolbox and then decide on the Devise gem.
There are risks associated with choosing Devise. As-of the creation of this video in October 2022, there hasn't been a commit to the main branch of Devise in over three months or a gem release in almost a year. And the current version doesn't work with Turbo or Rails 7 out-of-the-box at all and will need to be patched.
Still, it's likely the lowest amount of effort for the most value in return, and we'll roll the dice on it. (Pun intended.)
This video covers:
00:00:12 Introduction
00:00:59 Overview of the epic's GitHub issue and sub-tasks
00:03:42 Evaluate alternatives using the Ruby Toolbox
00:06:31 Review Devise on RubyGems and GitHub, risk of not receiving recent updates and not working with Turbo
00:09:41 Discussion of using UUID as primary key for User model instead of BigInt
00:11:08 Note on testing approach for this epic and need for browser driven system tests
00:12:43 Overview of the sub-tasks
#ruby #rails7 #rails #rubyonrails #rubygems #codecast #screencast #github #opensource #minitest #TDD #agile #NerdDice #DnD #roleplaying #softwaredevelopment #learntocode #tailwind #postgresql #rubocop #bundler #gemfile #rubytoolbox #devise
This video is CC0 - No rights reserved. (YouTube doesn't allow this option when publishing.) All code is released under the UNLICENSE. Stateless Code denies the concept of "intellectual property". Copying is not stealing.
