Uploaded January 2024 | Updated November 2026, 47 minutes ago
We have hundreds of coding videos here at Stateless Code, but almost all of them are recorded using the Ubuntu Linux distribution. We've invited you to code along, but maybe you're having trouble taking that first step because you're a Windows user and you don't know how to set up a development environment on Windows.
We've got good news! It has never been easier to set up a development environment on Windows. When I started learning Ruby, I would use VirtualBox to run a desktop version of Linux. In 2016, Windows released the first version of Windows Subsystem for Linux. It was a major improvement over needing to work on a desktop virtual machine guest, but it was still a bit clunky. Windows Subsystem for Linux 2 became generally available in 2020, and the experience for installing it has improved since then to the point where you can get it installed using one command on administrator PowerShell:
wsl --install
Once you run that command and reboot, you will be prompted to set your UNIX username and password for Ubuntu, and you're off and running!
But wait, there's more! If you have Visual Studio Code installed on Windows, you can install the Remote Development extension pack and interact with your Linux distribution from your Windows code editor.
After a few minutes, you can be up and running and code along with Stateless Code!
This video covers:
00:00:00 Introduction
00:02:34 Launch PowerShell as an administrator and execute `wsl --install` to begin the install process
00:04:20 Alternatives for manual installation if you don't want the default Ubuntu distribution
00:05:09 Reboot. Remaining portion of the Ubuntu install autolaunches when you log back in.
00:05:29 Increase the font size in the terminal and set the UNIX username and password
00:06:41 Update the software on Ubuntu with `sudo apt update && sudo apt full-upgrade -y`
00:07:22 Review the documentation on setting up a WSL development environment
00:08:46 Install Visual Studio Code on Windows (skip if already installed)
00:09:38 Launch VS Code and install the Remote Development extension pack
00:11:00 Re-launch VS Code and open the remote window to connect to WSL
00:12:05 Clone a Git repo in Linux and open it in the VS Code remote window
00:14:27 Quick overview of how preferences can be set at the Remote WSL level
00:15:24 Concluding thoughts
#codecast #screencast #github #opensource #softwaredevelopment #learntocode #windows #linux #wsl #wsl2 #ubuntu #windowssubsystemforlinux #vscode #visualstudiocode #remotedevelopment #powershell #unix
See other related StatelessCode videos:
- Setup and Configuration video playlist youtube.com/playlist?list=PL9kkbu1kLUeNWCKuMbpzE8r1xkx8L1Xf0
Resources that we relied upon for this solution:
- How to install Linux on Windows with WSL learn.microsoft.com/en-us/windows/wsl/install
- Manual installation steps for older versions of WSL learn.microsoft.com/en-us/windows/wsl/install-manual
- Set up a WSL development environment learn.microsoft.com/en-us/windows/wsl/setup/environment
- Troubleshooting Windows Subsystem for Linux learn.microsoft.com/en-us/windows/wsl/troubleshooting
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.
We have hundreds of coding videos here at Stateless Code, but almost all of them are recorded using the Ubuntu Linux distribution. We've invited you to code along, but maybe you're having trouble taking that first step because you're a Windows user and you don't know how to set up a development environment on Windows.
We've got good news! It has never been easier to set up a development environment on Windows. When I started learning Ruby, I would use VirtualBox to run a desktop version of Linux. In 2016, Windows released the first version of Windows Subsystem for Linux. It was a major improvement over needing to work on a desktop virtual machine guest, but it was still a bit clunky. Windows Subsystem for Linux 2 became generally available in 2020, and the experience for installing it has improved since then to the point where you can get it installed using one command on administrator PowerShell:
wsl --install
Once you run that command and reboot, you will be prompted to set your UNIX username and password for Ubuntu, and you're off and running!
But wait, there's more! If you have Visual Studio Code installed on Windows, you can install the Remote Development extension pack and interact with your Linux distribution from your Windows code editor.
After a few minutes, you can be up and running and code along with Stateless Code!
This video covers:
00:00:00 Introduction
00:02:34 Launch PowerShell as an administrator and execute `wsl --install` to begin the install process
00:04:20 Alternatives for manual installation if you don't want the default Ubuntu distribution
00:05:09 Reboot. Remaining portion of the Ubuntu install autolaunches when you log back in.
00:05:29 Increase the font size in the terminal and set the UNIX username and password
00:06:41 Update the software on Ubuntu with `sudo apt update && sudo apt full-upgrade -y`
00:07:22 Review the documentation on setting up a WSL development environment
00:08:46 Install Visual Studio Code on Windows (skip if already installed)
00:09:38 Launch VS Code and install the Remote Development extension pack
00:11:00 Re-launch VS Code and open the remote window to connect to WSL
00:12:05 Clone a Git repo in Linux and open it in the VS Code remote window
00:14:27 Quick overview of how preferences can be set at the Remote WSL level
00:15:24 Concluding thoughts
#codecast #screencast #github #opensource #softwaredevelopment #learntocode #windows #linux #wsl #wsl2 #ubuntu #windowssubsystemforlinux #vscode #visualstudiocode #remotedevelopment #powershell #unix
See other related StatelessCode videos:
- Setup and Configuration video playlist youtube.com/playlist?list=PL9kkbu1kLUeNWCKuMbpzE8r1xkx8L1Xf0
Resources that we relied upon for this solution:
- How to install Linux on Windows with WSL learn.microsoft.com/en-us/windows/wsl/install
- Manual installation steps for older versions of WSL learn.microsoft.com/en-us/windows/wsl/install-manual
- Set up a WSL development environment learn.microsoft.com/en-us/windows/wsl/setup/environment
- Troubleshooting Windows Subsystem for Linux learn.microsoft.com/en-us/windows/wsl/troubleshooting
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)



