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

Made progress on my Flask/Vuetify template that I want to try to sell.

Cloned my Flask/Vuetify template repo to start work on my "Let's Play" idea

Copied over my backend Go code from my go-vuetify-template repo to my whatdo repo and deleted the flask backend code, now I just need to see what functionality is missing from the Go backend code that was in the Flask code.

Got whatdo.com up-and-running based on my flask-vuetify template (viper.guru).

Started going through the "Let's Go" ebook, started my first Go web app.

Create a branch where I'm going to try getting the app looking nice with Vuetify because the #1 source of stuff taking a long time is that styling the app takes forever, and the projects I'm working on for my Upwork clients move way faster because I'm using Vuetify (at the expense of not looking as nice as a DAW or IDE desktop application). #rhymecraft

Spent an hour reading some of [the backend code][1] for a Go / Vue chat app I saw posted to Reddit, as a way of trying to build familiarity with how my Go / Vue projects should be structured / work. [1]: github.com/wizzldev/backend/

Got the app working where the Vuetify interface can exist at a different endpoint than the existing UI as a way of hopefully avoiding needing to fix all the CSS problems right now. #rhymecraft

Finally on WIP ⚠️ Need to add some projects. Rewrote the backend of one of my OSS projects into Golang from TS. Starting to build out the SPF flattening tool. #dnsbuddy

Got Vuetify working. #cleanexam

got my personal website (nathanwailes.com/, just an index.html) working on a new $4/mo DO droplet that I intend to move everything over to while switching backends from Python to Go, nginx is way easier than Apache so far. Switched my personal site to use GitHub version control.

Continuing to try to get Dokku working with a monorepo; I think I got past my last problem of how to deploy both apps by running on the server `dokku builder:set backend-app build-dir backend` (and similar for the frontend); now I'm seeing a new error when I try to deploy the frontend app: `Two different lockfiles found: package-lock.json and yarn.lock`; I seemed to fix it by deleting the yarn.lock. New error: "Missing script: start"; fixed that by adding a 'start' entry to my package.json. New error: "Cannot find module '@vitejs/plugin-vue'"; maybe because it's listed as a devDependency? I found this SO post where the guy said he ended up just putting his frontend on Netlify, so maybe I'll try that instead: stackoverflow.com/a/62455021/… ChatGPT is saying the way to do it is to deploy my API at api.mydomain.com and then direct traffic at other subdomains to Netlify to handle frontend requests. So I'll try that tomorrow.

Worked really hard on the boilerplate. Got it to a decent shape. Project is now fully generated by cookiecutter, need to do further testing to ensure tailwind is fully integrated, and then testing for deployments.

Spent time learning about using Go for a web app back-end to see if it would be better than using Python.

Cross Post dev.to/golangch/omg-i-love-to… #fullstackjob

Make progress on cloning WIP to practice full stack web dev #buildstreak

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

Felt too flu-ed out today to get much done, but added some style tweaks at least! I think next step is to just fork it and build the site I need for ketolistsingapore, keyboardsg and add more features to the boilerplate based on real world execution rather than dreaming up feature I need in the boilerplate in abstract #listskit

Make an iced cocoa (20g of pure cocoa, so as much caffeine as a cup of tea) by myself for the first time in my life; spent a ridiculous amount of time trying to figure out how to get Go to store my user password hashed; ran into an issue using the 'air' live reloader where it wasn't working after I redid the project structure, and it didn't have useful error messages or documentation to help me figure out what setting I needed to set to get it to work again; got past the air issue, it turns out I had to specify the directories to watch and without any leading "./"; created a user via the Vuetify app and confirmed that the password is hashed on the backend; created a Stack Overflow Q&A explaining how I fixed the issue for future newbies; committed my code. Set a goal for tomorrow: implement the authenticationHandler.