You could set this in your config to something like `Rails.env.development? || Rails.env.production?` or `!Rails.env.test?` to bypass it on the tests.

I think that this would be a great episode. In your example, would the token be used in addition to their username and password for multifactor auth? Or, are you thinking that the user would not have a username and password and they would simply authenticate with the token? Keep in mind that with security around authentication, ticking off more of these in the list below strengthens the auth wall. 1. something you know (username and password) 2. something you have (registered cell phone with app for token) 3. something you are (fingerprint, facial, etc. i.e., Touch ID to unlock phone) I would highly advise against using just a token to authenticate without needing the username and password if that was the direction you were referring to.

You could do it, but you'd likely be overwriting a lot of the devise gem. If this were the direction, I probably wouldn't use devise as it's including so much that wouldn't be applicable in this case. I'd still use the OTP gem as it would be able to handle generating and validating the token.

Hello! There is already an episode on Docker (https://www.driftingruby.com/episodes/intro-to-docker-on-windows). Even though it is on Windows, it is still very applicable to any OS; including macOS. Personally, I prefer using RVM without docker for my development environment. However, since I run macOS on my development machine which is very different from the production instance, I will periodically launch a VM instance to ensure everything is working properly. Since most of my applications are running the AWS Linux image (very closely related to Centos), I'll make sure that assets are precompiled and working properly. The bootstrapping scripts that I have to initialize new instances are tested in my VMs. Is there anything beyond this episode that you would like to see?

Are you able to verify that the doc is generated and at that location? You should be able to do an `eb ssh` within the root of your application to SSH into the environment. From there, look under `/var/app/current/public/docs` to see if it is there. If it is, check the URL to see if you're able to access the file. You may also need to edit your `config/environments/production.rb` file and set this entry `config.public_file_server.enabled = true`