Docker

We’ve seen now that we can run co-located and coupled services on Docker Swarm. This post shows you how to use templates to extend your services in a common way.

If we can run co-located containers on Docker Swarm mode, what can we use them for? This post goes through a few made-up example stacks, and explains the setup and the configuration of the components within the sort-of pods.

Emulating Kubernetes pods on Docker Swarm mode.

The final post in the series describes the various Swarm stacks I now have in GitHub, and explains the workflows around them.

A recent Docker update came with a small but important change for service secrets and configs, that enables a much easier way to manage and update them when deploying Swarm stacks.

Create and maintain DNS records on Cloudflare, secure the communication to the origin servers using certificates from Let’s Encrypt, and how to make this painless and fully automated.

Having looked at the configuration and setup of the services in the Home Lab, it’s time to talk about how we can monitor them, and manage their logs.

Let me explain the configuration method I use for my services and HTTP endpoints. Spoiler: it’s Docker and it’s automated.

This third post in the series explains how I extended my stack to multiple servers with Docker Swarm.

In the second post of the series I dive into the details of what is involved setting up for an ever-growing number of applications on a handful of physical servers on my Home Lab.