armchair dot tech
homelab | HOME | ABOUT | TAGS

Homelab Rebuild Part 2 (#homelab #rebuild #traefik #docker ) 2019-12-29
I realized so much of my reading on Traefik was based on 1.7 and I was running 2.0. I jumped ahead and set my image to 2.1.1 (latest as of this post). The big problem I had with that blog post was that for the main traffic instance with the redirect was not working. Because I have - "--providers.docker.exposedbydefault=false" I had to add these lines to the labels.

Homelab Rebuild (#homelab #rebuild #traefik #docker ) 2019-10-28
Background I have a homelab which has been grown organically with services installed by hand and placed randomly. I decided it’s time to rebuild it “in place”. Since this isn’t a production system, I have a lot of latitude in taking things down and redoing it. I do have a bunch of montoring data in influxdb that I want to keep, but most of the rest can go away. I’ll start first by figuring out what I have server wise.

documenting my homelab with openDCIM (#homelab ) 2017-03-28
Background I’ve been wanting to document my home and homelab network for a while now. I used to keep some individual files around with a list of ip addresses and networks, and I used to have a yaml file with the network laid out. But a lot of it was out of date and any time I made a significant change (like adding vlans or tagged interfaces), the entire format would need to change.

Worst Practice Lab VM Automation (#homelab ) 2016-09-05
Worst Practice Lab VM Automation I’ve started the process of switching my lab over from unmanaged to ansible. I’ve used Puppet and Salt quite extensively through work, but after a handful of false starts with the lab, I think ansible is the way to go.g his is a series of what many (including myself) would consider “worst practices”, but are more along the lines of “rapid iteration”. The goal here is to get something working in a short period of time, without spending hours, days, or weeks researching best practices.