Back to the main page

At home, running

My home server, set up as code

A Linux server at home for my own self-hosted services. Its setup lives in Git and one playbook, and I have checked two things: that the playbook and the machine agree, and that an alert really reaches me.

Built with: Linux, Docker Compose, Ansible, restic, Prometheus, Grafana, Tailscale (WireGuard)

Timeline of the alert test: target down at 0 seconds, alert at 36 seconds, cleared when the target came back.0 staken down36 salert firesback upalert clears
The alert test, on purpose. The figure leaves out what was taken down.

Configuration as code

  • Every service is its own Docker Compose stack, kept in Git.
  • One Ansible playbook sets up the whole machine: packages, users and SSH keys, SSH hardening, the firewall policy, Docker, the service stacks and the backup timer.
  • Running the playbook a second time in check mode has to report nothing changed. That is how I know the playbook and the machine agree.

Backups and access

  • Encrypted backups with restic, on a timer.
  • I reach the server over a private VPN.

The alert test

Prometheus watches the host and every container, and Grafana is set up from config files. To check that an alert really reaches me, I took a monitored target down on purpose: the alert fired 36 seconds later and cleared when the target came back.

What this page leaves out

Which services run on it, the hardware and the network layout. That is deliberate.

Contact

Reach me by email, in Swedish or English. References on request.

Languages: Swedish and English (fluent), Spanish (elementary).

Isak Mesihovic, Gothenburg.