Fixed an annoying db-related error with the #rhymecraft flask code that was causing it to error when I tried to query the API when running it on my laptop.

Switched my user and video-related API routes to use Flask_RESTX because it helps keep the API organized. #rhymecraft

Switched my Song routes to use flask_restx, and I now have all my routes using flask_restx. #rhymecraft

Spent some more time switching the API to using flask_restx. #rhymecraft

spend a bunch of time trying to understand how some boneheaded stuff works in Flask

Spent some time working on a 'home' route where I can link to different tools I create. #rhymecraft

fixed problem with routes (took 4 hours for a tiny mistake) #jesswallaceco

mostly finished the running website importer, updates templates, css, and a bunch of other housekeepting items #mylife

admin jobs, fix small bug in import routing #fullstackjob

cleaned up web routes file and running all the indexing/show functionality through the controller #jesswallace

fixed bugs and added updated routes #sponsorgap

Fixed a bug that was preventing auth from working in prod b/c Apache was stripping the auth header before passing it to my Flask app.

Doing boring work, migrating to new infrastructure

Remove unused routes; fix routing erros #jobician

Moved my API routes into a 'resources' folder to keep things a little more organized and since that's the pattern in the Flask-Vuetify template I like. #rhymecraft

switched the whatdo.com homepage to just be a simple list of links instead of the flask-vuetify template.

fix some route issues #turreto

deep dived into a django/python porting project and got quite a bit more done than I expected to. #mylife

Go: Switched my existing 'hello world' route/handler to use huma as a way of familiarizing myself with huma; checked out the huma-auto-generated /docs endpoint; spent ~90 minutes debugging an issue w/ how I defined a handler b/c the error message was not at all helpful; got POST /api/users (new user registration endpoint) working with the new setup (chi/huma).

today was my first day actually doing Go development instead of just tutorials: took a magnesium tablet b/c I felt anxious last night, I think from the caffeine in the cocoa I had been drinking; copied my frontend code from my flask/vuetify template repo to my go/vuetify template repo; confirmed I can serve the frontend code locally; installed Go; drank an iced cocoa; successfully started my 'Hello World' main.go backend file as a web app server; asked ChatGPT for help converting my "POST /users/" request to use Go; created a Go module; installed Postman macOS; took a 15min break after an hour; got my frontend app "talking to" my Go backend (successfully returned "Hello World" and had it on-screen in my frontend app); added Go middleware to log every request to the console so I can see what is happening; renamed my (default) branch from 'master' to 'main'; got live reloading for my Go backend (it automatically reloads the backend when I make changes to the code); confirmed my "POST /users/" returns 201 when I use the frontend registration form; came up with a task for tomorrow: get "POST /api/session" working; set up PyCharm to be able to explore my SQLite db from within the DB toolbar; confirmed that my user registration created a new user record in the db