DevOps / System Engineering

Linux-based platforms, container runtimes, and operationally clean delivery.

I build and document small, production-like systems with a bias toward clear runtime boundaries, practical automation, and recoverable operations. This site is the frontdoor to that work.

DevOps / System Engineer Germany shellr.net

Profile

Technical focus, not template polish.

My work sits at the intersection of Linux administration, web platform delivery, and operational discipline. I care about how systems are deployed, observed, recovered, and explained, especially when the environment is intentionally constrained.

This platform is designed to show the difference between "it runs" and "it is maintainable": explicit routing, bounded logs, controlled deployments, documented recovery, and infrastructure that can still be reasoned about by one engineer.

Featured Projects

Applied infrastructure work with visible trade-offs.

genesis platform

Single-VM platform on Hetzner with Docker Compose, TLS termination, deployment automation, monitoring, logging, and backup.

  • Linux
  • Docker
  • Nginx
  • GitHub Actions
  • Grafana
  • Loki
Documentation

DMA application

Legacy PHP application moved behind a controlled reverse-proxy setup with its own runtime path, database scope, and operational recovery path.

  • PHP
  • MariaDB
  • Nginx
  • Containerization
Open DMA

Observability layer

Prometheus, Grafana, Uptime Kuma, Loki, and Promtail sized for a small host with strict retention and bounded disk usage.

  • Prometheus
  • Grafana
  • Uptime Kuma
  • Loki
Status

Tech Stack

Core competencies that show up in the platform itself.

Linux operations and host hardening

Docker and Compose-based application delivery

Reverse proxying, TLS, and subdomain routing

CI/CD with GitHub Actions and SSH deployment

Monitoring, logging, retention, and incident visibility

Documented backup and restore procedures

Platform

What runs behind this frontdoor.

  • Single Hetzner VM with explicit runtime boundaries
  • Portfolio landing page on shellr.net
  • Dedicated DMA subdomain on dma.shellr.net
  • Grafana and status separated onto their own hostnames
  • Technical documentation published on docs.shellr.net via GitHub Pages

routing model

shellr.net          -> portfolio landing page
www.shellr.net      -> redirect to shellr.net
dma.shellr.net      -> DMA application
grafana.shellr.net  -> protected Grafana
status.shellr.net   -> Uptime Kuma
docs.shellr.net     -> GitHub Pages documentation