After switching to rodauth I was not quite happy with my implementation of the current_account feature. So I decided to dig a bit deeper into the documentation and found a really neat solution.

I was already using dry-effects, but in a rather haphazard way. Looking at the documentation again, I decided to go the rack middleware route as well. If I put the new middleware after rodauth, I can grab the account_id from request.env[“rodauth”] and store it in the effects handler:

I recently migrated a small app that I wrote to help me track ADHD symptoms from a very basic authentication with Warden to a rodauth based solution.

I am a big fan of rodauth, as it has the same design sensibilities as Jeremy’s other awesome gems, roda and sequel.

Since switching authentication systems is a bit trickier than adding one from scratch I thought it might be helpful to compile some of my notes for others who are planning to go on this journey.

This has taken me longer to figure out than it should, so I am writing this down in the hopes of saving other people some time and headache.