Homelab Adventures

Sign in Subscribe

Topic

homelab

A collection of 18 issues

Improving the Process

At this point, we have a small handful of containers running, and are likely looking at adding more to the list. It's only reasonable to consider the maintainability of the resulting system, and the fact of the matter is, the prospects of keeping going with individual containers on

Dogfooding it, Pt 4 - Traefik

Traefik is a reverse proxy with container integration. With properly set up containers and networking, it's minimal configuration to get it working in this lab - much easier than nGinx. Our directory structure for this consists of a handful of directories. We do need the Traefik UID to

Dogfooding it, Pt 3 - Ghost

At this point, we have a Docker server and a PerconaDB / MySQL container. It's time to install the Ghost CMS itself. First, we'll need to establish the database user for it. Ghost itself does not support a shared secret, so we're just going to

Dogfooding it, Pt 2 - MySQL

So it's technically going to be Percona Server. No real reason, it's just what I've been using for a long time. Could just as easily go MySQL 8. First, though, there's a few other things we have to take care of. Number

Dogfooding it, Pt 1 - Docker

Because I believe in eating my own dogfood with a publication like this, the first thing I'll demonstrate is showing how to set up the Ghost CMS on a Docker-based home lab server. Again, we'll start from the base system. I suggest using a physical host

Router Setup

For this, start with the base image and deploy to a system with two network cards. It's possible to use one and configure a "router on a stick," but that's a bit beyond the scope of this blog post. For the initial setup, only

Base System Setup

This step installs a very basic Arch Linux system to be used in later steps to build out the home environment. Depending on how you plan on doing things, you may need more than one of these - my personal setup runs on one firewall and one container host. I

Design Overview

At a high level, this environment consists of three networks: an outbound internet connection, the internal network hosting the lab server itself, and a docker private network connecting the containers. The outbound router can be a customer-grade device, but in the spirit of DIY, we will be setting it up