Hi, I'm Scott. I work across software engineering, enterprise infrastructure, Linux, and containers. I also build self-hosted tools for media servers, Docker, and Synology — usually because I got tired of doing something by hand and decided to make the solution everyone else's problem.

My natural habitat is somewhere between a tidy Compose file and a cron job I definitely remember creating.

1.21 gigawatts? Please. That's my homelab's idle power draw.

Shells, servers, containers, and the automation that keeps them on speaking terms.

Languages & shells

Linux & systems

Containers

Infrastructure & cloud

Build & delivery

Applications & data

Networking & monitoring

AI tools

Bash, sh, Zsh — if it has a prompt, I'm probably happy. I develop on macOS, work across Linux distributions, and spend an unreasonable amount of time making Docker Compose behave politely on Synology. YAML and I are in a long-term relationship. We are seeking counseling.

My work includes CI/CD, GitOps, infrastructure as code, and keeping services reliable. I also work with AI APIs, MCP, and agents. The tools can help write the code; they don't get custody of the production credentials.

Plundarr turns the media apps you choose into a complete Docker Compose deployment. It sorts out dependencies, writes the Compose and environment files, and validates the result before launch. It can build movie and TV automation stacks, standalone Plex or Jellyfin setups, or a custom fleet for Docker and Synology Container Manager.

You choose the cargo; Plundarr handles the rigging. Much less archaeological digging through abandoned Compose snippets at 2 a.m.

Privateerr puts Private Internet Access's official connection scripts into a small Docker image. It generates a WireGuard configuration and the server details that Gluetun—or another compatible VPN client—needs to connect, including the awkward bits required for port forwarding.

Privateerr is not the VPN client. It does the paperwork, hands Gluetun the map, and leaves before networking gets emotionally complicated.

I care about the unglamorous stuff that makes self-hosted software pleasant: sane defaults, reproducible deployments, clear docs, and error messages that tell you what actually broke.

Questions, cursed logs, or a container that has slipped out of the timeline? Come say hello in HADES. Bring logs and snacks.