Got auth working on my "let's play" repo by copying the code from my "let's read" repo

Copied my auth code over to my main whatdo repo, I want users to have a single account across all my app ideas to reduce friction to try new apps, craigslist-style.

Copied over the frontend changes needed to get the auth working from my #govuetifytemplate to my #whatdo repo

Go: Bought "Let's Go Further" b/c it has a section on authentication for API backends; read that section; notice he has the code in his project set up differently than mine; rearrange my project directory structure to match the book's recommendation; spent some time looking at how he does authentication in the book; decided that I should maybe instead try to follow the Huma guide to doing OAuth 2.0: huma.rocks/how-to/oauth2-jwt/

Add auth #myga

worked on moving the GitHub App to manage #djangopackages auth

Read up on auth implementation

Added auth on main app #renzi

🤖 cleaned up a few automation projects and outsourced auth to GitHub Auth

📝 Hooked up GitHub auth/login and configured my app to create accounts by email address #conf

add codesandbox so people can test auth when following along #serverlesshandbook

give @felpsio auth access #serverlessreact

set up auth on app #chamados

Did some auth update planning and wrote PoC #mobius

Added Github oAuth login to #connectify

Add in auth code #createpin

Handle two different authentication methods: via oauth app and via github app (required for private repo support) #devhub

⚙️ connected GitHub auth and did some additional template and plumbing updates

Got an auth-protected API route working

Researched, read up on PHP API authentication - normal user auth for login/signup is simple enough but protecting api endpoints and access control is the key step to moving fwd for my approach #indiejourney #decodingcoding