Spent an hour going over my app ideas to try to decide on what to work on next, settled on trying to build a Line+ChatGPT bot that will run on my Dokku droplet.

Worked on getting ChatGPT working with the Line echo bot example...created a separate file to test the OpenAI API call...hit an error, turned out I needed to pay separately for API credits...hit another error from my request not being formatted properly...finally got it working, now I need to try to integrate it with the Line echo bot...updated the code to use the ChatGPT code and deployed it, but the bot isn't responding anymore, I need to examine the logs...checked the logs with `dokku logs api` (`api` being the name of my app) and saw the error: "You didn't provide an API key."...need to add my API key as an env var...got that added with `dokku config:set`...tested the echo bot again and IT WORKED. It is insane insane insane how fast I can get stuff working when I can ask ChatGPT for help at every step to cut through all the usual Googling to figure out how to do something...next up, hmm, I'm not sure, either work on an accompanying Vue frontend or try fleshing out the bot to handle the particular use-case I have in mind...sent an email to another YouTuber to see if I can do a video with him.

Struggled to incorporate the Line "echo bot" code into my existing Huma Go backend framework code, so I just YOLO'd it and copied the example code into my `main.go` for the purpose of seeing if I can get it working...ran into an error when pushing to Dokku, it seems to be because I didn't set the Line-related env variables before pushing...set those vars on my Dokku server...clicked the Line 'Verify' button for the callback URL and got a 404, so I now need to look into what happened...I think the issue is that the echo bot code assumes I'll use the DefaultServeMux, but I'm actually using a chi Mux. The key line difference is `log.Fatal(http.ListenAndServe(":"+port, r))`, where the example has `nil` instead of `r`...YOLO'd it again by just disabling the router I had gotten working, just to see if the webhook will work, and got a Success when I clicked the Verify button...next up is to either clean up this mess I've made in my code or keep pushing forwards and try to get the ChatGPT part working.

Only got ~5hrs of sleep after two double espressos yesterday, so I took a Lycopene capsule...signed up for a LinkedIn Premium free trial so I could send a message to a Kasikorn backend engineer to ask why users can't export their transaction history in CSV format...removed the 'Blog' link on nw.com b/c I don't have the WordPress blog up and I never really used the blog that much, added a link to my email address instead so people can contact me...started going through the Kasikorn API "Slip Verification" challenges...got the first one done...the second one requires I have SSL set up on my domain and not through Cloudflare...discovered while doing that that my whatdo site is returning a 404 if I try to sign in...got GoLand's db tool connecting to the digital ocean postgres db b/c I noticed that wasn't set up yet...install postgres on my macbook b/c something got messed up and somehow it seemed to not be installed...got all the db problems fixed, don't know how that happened...now having a CORS issue when running locally, all this stuff was working, IDK how it all broke...ok I remember now, I YOLO'd the backend code and disabled the existing router to get the Line echo bot working...sent an email to another local YouTuber to ask if I can be in a video with him...installed cursor and tried using it for a simple refactor task to get a sense of how it works...figured out a way (thanks to ChatGPT) to get the Line callback handler working while also not breaking the existing routes...went for a massage to give my brain cells some time to recover...used cursor some more and I get the hype, this is really cool, I'm surprised Jetbrains hasn't copied it yet...after a long while I finally got my whatdo backend working properly again (auth + user middleware working), it was a good learning experience with cursor and Go...got a GitHub Action set up so my DO dokku VPS will update when I push to main, so now both frontend and backend will update automatically when I push to GitHub...ending the day on this banger set: www.youtube.com/watch?v=d2340… Tomorrow: I need to bill hours to my client to make $, I want to try to finish the KBank API challenge to see if I can do the Slip Verification, I want to email another YouTuber, if I have any time left over I want to keep going with that Line/ChatGPT bot and try to make a frontend interface for it.

Worked on a first draft of a 1-page "how to hire and manage remote workers" PDF that I want to start sending along with my resume and possibly also use as a marketing thing for my Wailes & Company remote work management consultancy idea...drank a double espresso ~4-5hrs before my expected bedtime, I hope I don't regret this...emailed another YouTuber but w/ a slightly different email approach...continuing to learn how to use Cursor, resolved a deploy.yml error by signing into GitHub after some Googling to understand what was going on...spent a while breaking up my backend code into sub-app directories as a way of setting the stage to work on multiple app ideas at the same time, and also to continue to build familiarity with Go since I'm still very new to it...spending the time after the caffeine high has kind of worn off (3hrs post-double-espresso) just thinking about what I should work on next...decide on some next small steps for tomorrow: 1) be able to query the Algolia HN API and get back the list of HN jobs, 2) set up a new db schema for the jobs app, 3) figure out how to best use ChatGPT to analyze the different job posts (individual queries vs. some kind of batch request).

(Try) to put NodeJS Flight Ticket Telegram bot on Digital Ocean Droplet. Ragequit for today after droplet 1 has strange connection / dependency issues. Restoring back-up removed new SSH key 🤡. Figure out I'll use Docker on droplet 2. Fight DO container registry auth issues and call it a day... #dev

Started learning Dokku / trying to set it up with Digital Ocean. ty @ben ... joined the dokku discord; went through this guide: dokku.com/docs/getting-starte… ; switched my whatdo domain in DigitalOcean to point to the new dokku droplet ; asked for help in the forum to understand what it means for "the web UI [to be] submitted": github.com/dokku/dokku/discus… ; I think it's referring to the DO UI for creating the new droplet ; next step for tomorrow: go through this guide: dokku.com/docs/deployment/app…

Finally got the Dokku Ruby on Rails example app working 😭 Apparently I just needed to reboot the droplet? `curl` to my droplet's IP wasn't working, `dokku ports:list ruby-getting-started` didn't show it listening on port 80, `dokku ports:add ruby-getting-started http:80:5000` resulted in an error saying nginx wasn't running. Rebooting seemed to fix it. Next up is trying to deploy my Go backend with Dokku. Destroyed the ruby demo dokku app. Resized my DO droplet to the $6/mo one.