Go to file
Elara d01edf7e54 Update LICENSE 2023-07-29 21:36:07 -07:00
authelia Update domain 2023-07-29 21:32:34 -07:00
gitea Update domain 2023-07-29 21:32:34 -07:00
go-import-redirector Update username 2023-07-29 21:33:23 -07:00
homer Update domain 2023-07-29 21:32:34 -07:00
lms Update domain 2023-07-29 21:32:34 -07:00
lure-web Update username 2023-07-29 21:33:23 -07:00
minio Update domain 2023-07-29 21:32:34 -07:00
nextcloud-onlyoffice Update domain 2023-07-29 21:32:34 -07:00
searxng Update domain 2023-07-29 21:32:34 -07:00
traefik Update domain 2023-07-29 21:32:34 -07:00
woodpecker-ci Update domain 2023-07-29 21:32:34 -07:00
LICENSE Update LICENSE 2023-07-29 21:36:07 -07:00
README.md Update 'README.md' 2022-11-19 23:56:26 +00:00



This repository contains my Nomad and Consul configurations that I am using for my servers.

Nomad is an orchestrator. It orchestrates a cluster of multiple computers to perform a certain task. Consul is a service discovery solution as well as a key/value store. Nomad seamlessly integrates with Consul to provide a cohesive solution that works really well.

I have a cluster of 8 Raspberry Pi 4s (4x 1GB, 4x 2GB RAM), 2 2GB Pine H64s, 1 2GB RockPro64, a 16GB Radxa Rock 5 Model B, and a 2012 Mac Mini with an i7 that I've upgraded with a 1TB SSD and 16GB of RAM.

I'd originally planned to use Kubernetes on this cluster, but due to the low power and especially low RAM of many of my nodes, Kubernetes would either take up nearly all the resources or freeze the nodes entirely, forcing a hard reboot. Recently, I found Nomad, which is far more lightweight, while providing more features. In my opinion, the only downside is the fact that Kubernetes has a much bigger community.

Using Nomad is great, and much better than my previous strategy of "stick everything somewhere and hope you remember where". All I do is create one of these nomad files, using the very good documentation for Nomad, and then submit it to Nomad. Nomad then automatically decides where to put the service, installs it, configures it, runs it, and publishes it to Consul, from where Traefik picks it up and reconfigures itself automatically to point to the newly-created service. If the service is stateless, like a few of mine are, then Nomad can seamlessly migrate the service to another node, and Traefik will reconfigure itself automatically to point to the new node.

The way I have my cluster set up is: My mac mini acts as the only Nomad and Consul server in the cluster because it has the most resources. Each node in the cluster has a Nomad client running on it, as well as a Consul client. They are simply services installed by the package manager and run by systemd.

A couple of my services are running outside of Nomad because they have a complex config, or because they're Home Assistant, which has a supervisor docker container that launches other docker containers, etc. and I don't know how to express that in a nomad job file. For these, I use a simple systemd service that runs consul register with the service's information. This causes Traefik to pick them up and automatically reconfigure itself the same as it does for Nomad servces.

Before using any files in this repo, read through them and make sure to replace anything that is mentioned on the individual READMEs, as well as things like domain names. My domain is arsenm.dev, so change anything that has that to your domain instead,