/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

www.joshkasuboski.com
| | paul.totterman.name
1.7 parsecs away

Travel
| | Like many other developers, I have to work with computers with different processor architectures. For me it's amd64 (x86_64) on the laptop and arm64 (aarch64) on the server. For some it may be the other way around. Fortunately I mostly write Go, which makes cross-compilation quite easy. Docker adds some extra steps, but is very nice for deploying software.
| | actuated.dev
3.8 parsecs away

Travel
| | Learn how to publish container images for both Arm and Intel machines from GitHub Actions.
| | hjr265.me
4.0 parsecs away

Travel
| | I began the weekend writing a silly program: MGHSIAC. It's the elegant abbreviation of "My GitHub Status Is A Clock". It turns my GitHub status into a working clock. You can read more about it here. But as silly as it is, I am now committed to keep it running. I have an always-on Raspberry Pi with Portainer running on it already. If I could make a Docker image and host it on Docker Hub, I could easily pull it to that Raspberry Pi and have it continuously update my GitHub status with clock emojis and messages.
| | hjr265.me
10.7 parsecs away

Travel
| Docker has been providing a health check mechanism for quite some time. It is useful in identifying issues with programs that can fail in ways other than just outright crashing. And it is easy to set up. Docker health checks work periodically running a program within the container and observing its exit status. If it exits with a 0, the container is considered healthy. If it exits with a 1, the container is considered to be unhealthy.