So, currently my tech setup looks like this:

Education is only a ladder to gather fruit from the tree of knowledge, not the fruit itself. Austin O'Malley

Here’s an easy way to manage updates of containers using Dockpeek and Portainer: Open Dockpeek and click the Check for updates button For each container shown as needing updates, use the following steps: Go to the Stacks page Click on the first container needing an updated Click on the Editor tab Scroll down and click on the Update the stack button On the Are you sure? pop-up, click the Re-pull image and redeploy slider to ON and click the Update button

From Futility Closet

From time to time, it’s necessary to access a computer remotely. Over the years, TeamViewer was the tool of choice, but it has fallen into a bloated annoyance recently, so for many moons now I’ve been using Rustdesk - a FOSS toolset that works ideally for my use cases.

My daily-driver is an Asus X515 laptop running Windows 11. I picked this up a few years back when it was on sale at a good price, knowing it was a little underpowered for my long-term needs.

I use Syncthing to synchronize files between various systems in my extended homelab. There are currently five systems using Syncthing - a primary NAS server and a backup NAS server based in Texas, a laptop running Ubuntu Server 24.04 currently based with me in Ireland (and known as the Blackrock server), my personal Asus laptop running Windows 11, and a Digital Ocean VPS running Ubuntu Server 24.04. (I have a couple of other devices in the Tailnet - my Pixel 6 phone, and the travel Chromecast.)*

Before we came to Ireland for extended stays, I setup an old Dell laptop to be the media server while we travel. This system runs Ubuntu 24.04 Server with a GUI, and makes it possible for us to watch our ripped movies and related media. I use Tailscale to securely access my remote systems, and in the Tailnet this server has the uninspired hostname of dell4800.

I use the vim editor to write these posts, and prefer not to use vim’s automatic line-wrapping. There are times when longer lines are necessary, so I like to manually wrap lines when needed. In blog posts like this, paragraphs are separated by a blank line. To wrap the lines in a single paragraph, use this key sequence: :gq} : opens command mode, gq is the wrap command which must be followed by a movement command. } moves to the next empty line. Put them altogether and the current paragraph is wrapped to the defined line width, which defaults to 80.

Over the last week or so, I’ve enjoyed updating the tools I use for this site, which is built using Hugo. Hugo creates static HTML from Markdown source, and is perfect for low volume sites that are updated on an occassional basis, and that hasn’t changed. The tooling I use to host the site has changed, along with the method i use to upload the new HTML to the web host.