Uploaded October 2022 | Updated November 2026, 3 hours ago
After installing Devise in the previous video, we add the required configuration and customize the configuration to match the preferences for the app.
We delve briefly into working with Rails views and layouts using embedded Ruby in HTML (html.erb) and using Tailwind Play to validate the styling classes we are using.
After that, we configure a Devise secret key and pepper using Rails encrypted credentials on a per-environment basis. We walk through creating those files and how to access the attributes. (Then we change the attributes we displayed on-screen before committing so that there isn't an encrypted and decrypted version of the file available on the internet.)
We go through the rest of the configuration options, making changes based on preferences for this application.
After fixing some RuboCop offenses, we create a GitHub Actions version of our test credentials file and use GitHub repository secrets to get the file into our build.
This video covers:
00:00:12 Introduction
00:01:39 Configure default_url_options in environment files
00:03:32 Add flash messages to application layout and use Tailwind Play to double-check them
00:08:30 Set up Devise secret_key and pepper using Rails credentials for various environments
00:20:20 Customize the other attributes in the Devise configuration file to match preferences for the app
00:29:18 Run RuboCop, correct offenses, add exclusions
00:33:08 Create a specific credentials file for GitHub actions
00:38:27 Modify main.yml build to copy GitHub Actions version of credentials
00:40:26 Use repository secret to copy GitHub Actions key for credentials into the build
00:42:00 Commit and first build attempt
00:45:22 Build failed, remove master key environment variable from main.yml build
00:47:17 Mark sub-task complete
#ruby #rails7 #rails #rubyonrails #rubygems #codecast #screencast #github #opensource #minitest #TDD #agile #NerdDice #DnD #roleplaying #softwaredevelopment #learntocode #tailwind #postgresql #rubocop #bundler #gemfile #devise #turbo #githubactions #railscredentials
See other related StatelessCode videos:
- Install Devise 4.8 on a Rails 7 Application youtu.be/CbWwqLK8T1Q
- Set up GitHub Actions with Rails 7 and Get Working with PostgreSQL youtu.be/sIfGSdQvODU
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.
After installing Devise in the previous video, we add the required configuration and customize the configuration to match the preferences for the app.
We delve briefly into working with Rails views and layouts using embedded Ruby in HTML (html.erb) and using Tailwind Play to validate the styling classes we are using.
After that, we configure a Devise secret key and pepper using Rails encrypted credentials on a per-environment basis. We walk through creating those files and how to access the attributes. (Then we change the attributes we displayed on-screen before committing so that there isn't an encrypted and decrypted version of the file available on the internet.)
We go through the rest of the configuration options, making changes based on preferences for this application.
After fixing some RuboCop offenses, we create a GitHub Actions version of our test credentials file and use GitHub repository secrets to get the file into our build.
This video covers:
00:00:12 Introduction
00:01:39 Configure default_url_options in environment files
00:03:32 Add flash messages to application layout and use Tailwind Play to double-check them
00:08:30 Set up Devise secret_key and pepper using Rails credentials for various environments
00:20:20 Customize the other attributes in the Devise configuration file to match preferences for the app
00:29:18 Run RuboCop, correct offenses, add exclusions
00:33:08 Create a specific credentials file for GitHub actions
00:38:27 Modify main.yml build to copy GitHub Actions version of credentials
00:40:26 Use repository secret to copy GitHub Actions key for credentials into the build
00:42:00 Commit and first build attempt
00:45:22 Build failed, remove master key environment variable from main.yml build
00:47:17 Mark sub-task complete
#ruby #rails7 #rails #rubyonrails #rubygems #codecast #screencast #github #opensource #minitest #TDD #agile #NerdDice #DnD #roleplaying #softwaredevelopment #learntocode #tailwind #postgresql #rubocop #bundler #gemfile #devise #turbo #githubactions #railscredentials
See other related StatelessCode videos:
- Install Devise 4.8 on a Rails 7 Application youtu.be/CbWwqLK8T1Q
- Set up GitHub Actions with Rails 7 and Get Working with PostgreSQL youtu.be/sIfGSdQvODU
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.



![Upgrade to Devise 4.9 on Rails 7 and Decommission the 4.8 Hacks
Some exciting developments have taken place while we were working on our RubyGem! Devise released a new minor version 4.9 that works with Rails 7 and Turbo without requiring a custom responder class or TurboDeviseController.
We intentionally held off on doing the upgrade in our video and commit where we upgraded to Ruby 3.2.1 and Rails 7.0.4.3 to isolate the Devise change. (We even needed to modify our Gemfile.lock to explicitly hold the Responders gem back at 3.0.1 because it was breaking our system tests.)
Situations like this illustrate why its so important to have a robust automated test suite. In the devise epic, we created system integration tests for all of our Devise scenarios so that we could discover whether the upgrade attempts would cause a breaking change or not.
To upgrade our app, we refer to the How To: Upgrade to Devise 4.9.0 [Hotwire Turbo integration] guide on the Devise Wiki. We start by removing the hacks we introduced to get Devise 4.8 working with Turbo and Rails 7. We delete our custom TurboDeviseController file altogether and remove the custom failure app code from our initializer.
We already modified the views to work with Turbo, so we can skip that part of the upgrade guide. The actual code change to upgrade to Devise 4.9 once we roll back our hacks is fairly simple. We just need to add configuration options for config.responder.error_status (:unprocessable_entity) and config.responder.redirect_status (:see_other).
When we run our full test suite, there is one failure. We investigate the screenshot and development environment of our application. It looks like the flash message for a blank email when Devise is configured to paranoid mode has changed. Were okay with the change, and modify our LogInLogOutTest for blank email to expect the new behavior.
This video covers:
00:00:12 Introduction
00:01:59 Check out the Devise pull request that fixes the Rails issues and the commit to our project where we introduced the hacks to get it working with 4.8
00:04:17 Update the Gemfile to use Devise 4.9.0 and run `bundle update`
00:05:15 Debug gem dependencies were blown away by the general `bundle update`. Reset to Gemfile.lock to HEAD and just run `bundle update devise`
00:07:34 Git Remove on the TurboDeviseController (git rm app/controllers/turbo_devise_controller.rb)
00:07:55 Remove the hacks from the Devise initializer configuration file (config/initializers/devise.rb)
00:10:04 Add in the new configuration options needed for config.responder.error_status and config.responder.redirect_status
00:11:36 Run the full test suite and investigate the one failure
00:13:56 Pull up the scenario in localhost development environment and see what happens. Determine that the change in behavior is acceptable
00:15:26 Modify the test to use the new flash message and refactor out the flash error text into an instance variable
00:16:52 Re-run tests to ensure everything is passing consistently
00:17:55 Review the git diff, run RuboCop, and commit
00:20:25 Remove missed TECH DEBT comment and amend the commit
00:21:52 Push to the branch, pull request, close issue
#ruby #rails7 #rails #rubyonrails #rubygems #codecast #screencast #github #opensource #minitest #TDD #agile #NerdDice #DnD #roleplaying #softwaredevelopment #learntocode #tailwind #postgresql #rubocop #devise #turbo #controllers #views #selenium #capybara #systemtest #debug #responders
See other related StatelessCode videos:
- Playlist: Using Devise 4.8 on Ruby on Rails 7 with Turbo and Tailwind https://www.youtube.com/playlist?list=PL9kkbu1kLUeMnvkrX7EOLSv6glmQzGMXL
- Get Devise Working with Turbo in Rails 7 https://youtu.be/xnuA2K2mohs
- Upgrade to Ruby 3.2.1 and Rails 7.0.4.3 https://youtu.be/XvRzpoWfM9Q
Resources that we relied upon for this solution:
- Devise pull request to fix Turbo https://github.com/heartcombo/devise/pull/5548
- How To: Upgrade to Devise 4.9.0 [Hotwire Turbo integration] https://github.com/heartcombo/devise/wiki/How-To:-Upgrade-to-Devise-4.9.0-%5BHotwire-Turbo-integration%5D
This video is CC0 - No rights reserved. (YouTube doesnt allow this option when publishing.) All code is released under the UNLICENSE. Stateless Code denies the concept of intellectual property. Copying is not stealing. Upgrade to Devise 4.9 on Rails 7 and Decommission the 4.8 Hacks](https://i.ytimg.com/vi/niNuwTu0URs/mqdefault.jpg)






