On this day - 2025-11-02
Today was one of those days where I didn't have much explicitly planned beforehand, so I decided to tackle some lingering items from my backlog. I completed my usual morning routine and had breakfast.
Sunday Tasks and Epiphanies
After checking my to-do list, I realized I needed to finalize and send my weekly log to my manager. I normally send this every Friday, but I hadn't been in the mood to make it then. This log details what I’ve done, any challenges or blockers I faced, and my goals for the upcoming week.
Since it was Sunday, I also went to get foodstuffs. I make sure to do this every Sunday so I can meal prep for the week. Luckily, the supermarket is very close, and the walk there serves as my morning constitutional—walking slowly, no music, comfy clothes, just time to think about life.
During that quiet morning walk, I suddenly remembered a crucial task: I needed to send my placement visit form to my university. This form schedules the date for my placement tutor to meet with my manager to discuss my placement progress, goals, and objectives. The visit is scheduled for this month, and if I hadn't gone for that walk, I genuinely don't think I would have remembered it—this is why I appreciate my morning walks. I also realized I have some work-related learning tasks that I prefer to complete during the weekend so my weekdays aren’t too busy.
Technical Shifts and Homelab Monitoring
Later in the day, I discovered that Agenix created a new secret management tool called ragenix, which, judging by the name, is written in Rust. I'm a sucker for performance, so I spent a few minutes switching to ragenix. The switch was quite easy, as the commands are mostly the same, though a few minor things seemed missing, which I anticipate will be in the next release.
I’ve been heavily involved in monitoring and alerting at work lately, which is a very important part of our infrastructure. This prompted me to set up monitoring in my own homelab. I decided to spend some time setting up uptime-kuma. I followed the Docker approach, making the setup quite easy. For now, I only have it configured for bare HTTPS monitoring for my blog and a simple Discord alert if the blog goes down. I'm looking forward to learning more about uptime-kuma and its benefits, especially the status-page feature, which allows the public to see monitored services, downtime, and custom messages.
Finally, I read a few blogs where I learned about devDoc.io.