Infrastructure

In this post, I shared my Traefik configuration. Back then, I’d just learned about Traefik and followed a few posts to set things up and get them working with all of my containers. Since then, I’ve used Traefik for every new container I’ve set up, I’ve run servers like Minecraft and 7 Days to Die through it, as well as numerous different DevOps-adjacent containers. So whilst I’m no means an expert, I’m definitely a little more adept at some of its configuration nuances (I’ll be publishing something next week about how to globally disable TLS 1.0 and 1.1 so keep an eye out for that). ...

The previous post on this topic is still relevant, however, since my selection of a new reverse proxy, I felt it necessary to publish an update. Assumptions You know what HTTPS and SSL certificates are/do and how the CA ecosystem works You have a domain that you plan to use for the Jenkins instance and this domain either doesn’t have a CAA record or has one that allows LetsEncrypt You understand the general working of containers and have docker installed on your system. Docker/Docker Compose knowledge is a plus but not required, you can basically just copy/paste code to get this working. I’ll also go over some common pitfalls at the end You either have your own reverse proxy setup and can handle this or you’re using my Traefik config You know what Jenkins is and why you should be using it. If you don’t, use the Google machine OK, let’s get this show on the road. ...

Twitter? Garbage. Facebook? Garbage. Do you enjoy having your data harvested and sold? No? Good. Back in the day, there was this thing called Internet Relay Chat. What if I told you… It still exists! Internet socializing without all the Silicon Valley data theft! But due to how the ecosystem works, any time you’re not actively connected to the server, you don’t receive any messages. This means that you don’t get to see conversations that happen while you’re offline, even if somebody mentions you! ...

So I had a need earlier on today. The need for simple end-user notifications. This need has some backstory, however… The plex container that I run on Docker is basically bulletproof. It does everything super quickly and is easy to restart for updates or to clear out some disk I/O issue with my NAS. The NAS is the only thing that’s really causing it issues because it’s a 5 year old Drobo which is in serious need of an upgrade! So if the Drobo locks up and kills all of the I/O to it, the containers need a reboot. Oddly enough, the Drobo itself doesn’t need a reboot (or even to be remounted) but that’s an investigation for another day. Here, we come to my need: to alert users when the container was ‘down for maintenance.’ ...