Today is my last Sunday off for the forseeable future. I started a new job the week before last and my permanent schedule goes into effect this week. It's retail, which I am not super thrilled about but so far it's not bad by any means. And you know, the week before I started my unemployment ran out so I'm happy to have literally anything. It's full-time, I get a day off with Ari and the pay is comparable to what I was making back home. Despite all that, I hate to admit that I'm already feeling pretty worn out; I think that's mostly because I've only gotten single days off since starting, plus I'd been sitting on my ass for the last 7 months. Regardless I'm thankfully going to be off Wednesday and Thursday.
Anyway, I digress. I'm spending today writing some code after not really having the time or energy to do it all week. I have a number of static sites I maintain all using the same methodology, which is to say they're plain HTML + Caddy templates, sometimes Sass and sometimes TypeScript. I'm sure there are a million existing tools I could have used to automate my deployment process, but I didn't want to bother looking around. Originally I wrote a Bash script to solve my deployment woes, but that's already become annoying to maintain. Taking that approach left at the whims of tools commonly found on a Linux system and their weird quirks. So instead, I'm taking the time to rewrite the script in Go.
It's weird to think this year marks my tenth since really diving into programming. It's weird to think that it's been 7 since I really took a dive into Go. I think if you showed 16 year old me what [she] would eventually be capable of creating, [she] would be proud. Anyway, I digress. I'm rewriting in Go; it was a pretty simple script which makes it a pretty simple Go program too. It relies on Git for transport and deployment, and thankfully Go has a pretty solid implementation of Git. Given a git compatible URL, the program will clone/pull the site repository and determine if it needs to deploy by checking the repository's tags. If it does, it will begin by copying static files, templates and any HTML files within the repository. If a .bakrad_include file is present at the root, it will copy any additional files that match the path/globs found on each line (much like a .gitignore). If a scss/main.scss file is present, it will compile that to static/css/index.css. If a ts directory is present, it will compile that to static/js. I'm not super happy with the functionality for those because they rely on wrapping external binaries with os/exec. I don't really have any alternatives until tsgo has a stable API available. Anyway, it's a low stakes project and I'm really enjoying working on it. The source is available at my forgejo if you're interested for some reason.
Other thing I've worked on today is this very site. I decided I did not like the format I was using in the URL, so I opted for the more traditional /year/month/day/title format. I took the opportunity to fix some small issues with the last blog post from March and also got it using the new url format. Oh and my friend posted a link to standard.site; it's a standard (wow) for sharing long-form content on the AT protocol. I'm not interested in supporting a ton of different standards for different sites and whatnot, but I am on bsky so I suppose it's worth it in this case.
Other than that, I'm taking my day to catch up on the week and breathe. We went and got some pet food this morning and stopped by a liquidation place. They had some cool things I'd like to have when I have money. We also stopped & grabbed some donuts on the way home. They were pretty good.