Back to the galaxy

01 Infrastructure & Systems

The foundationeverything runs on.

Linux servers, database architecture, CI/CD pipelines, monitoring. I build the layer everything else runs on — and keep it online.

99.9%
Target Uptimeacross managed deployments
24h
Response SLAcritical incidents
0s
Downtime on Deployblue-green releases
100%
Automated Backupsdaily · 30-day retention

02 What I Build

EVERY LAYER OF YOUR STACK.

From a bare VPS to a monitored, self-deploying platform. Built to be boring in the best way — it just stays up.

01

Linux Server Setup

Ubuntu / Debian / CentOS provisioning, user management, firewall configuration, SSH hardening, and automated security patching. Your server, production-ready from day one.

02

Database Architecture

MySQL, PostgreSQL, and Redis schema design, indexing strategy, replication setup, and backup automation. Built for performance at scale, not just for now.

03

Deployment Pipelines

GitHub Actions, Docker containerisation, and automated CI/CD workflows. Push to main, watch it deploy — zero manual steps, zero downtime, full rollback capability.

04

Nginx & Reverse Proxy

Nginx configuration for multi-domain hosting, SSL termination, load balancing, and rate limiting. Serving multiple applications from a single server, cleanly.

05

Docker & Containerisation

Dockerise your entire application stack. Compose configurations, registry management, and container orchestration. Same environment from local to production.

06

Monitoring & Alerting

Uptime monitoring, error tracking, performance dashboards, and on-call alerting. Know when something breaks before your users do — and get detailed diagnostics instantly.

03 Live demos Simulated server

YOU SEE EVERYTHING. IN REAL TIME.

Go on — break it. Every deployment comes with monitoring built in. I configure alerts on the thresholds that matter, so you hear about it before your users do.

Demo A · Incident simulator

Throw a problem at the server.

Spike the traffic, crash a container, fill the disk or start a flood. The alerts fire, the automation fixes what it can, and the incident log tells the story.

  • CPU, memory, disk, network and service health on one screen
  • Alerts on the thresholds that matter, sent to Telegram or email
  • Self-healing: auto-scale, container restarts, log rotation, rate limits
server-monitor — prod-01All systems nominal

CPU · memory · requests/s (last 2 min)

Cause an incident:

        

Demo B · CI/CD pipeline

Push to main. Watch it ship.

Every push is linted, tested, built into an image and rolled out blue-green: the new version warms up next to the old one, traffic shifts over, and a failed health check rolls back on its own.

  • GitHub Actions: lint → test → build → deploy
  • Zero-downtime blue-green traffic switch
  • Automatic rollback — tick “ship a bug” to see it
.github/workflows/deploy.ymlRunner ready
    BLUEv2.4.1 · live
    100% → blue
    GREENidle
    
            

    Demo C · Nginx config generator

    A production server block in ten seconds.

    Pick your domain and the features you need — HTTPS, HSTS, compression, WebSockets, caching, rate limiting and security headers. The config updates as you click, ready to review and paste.

    • The same defaults I ship on client servers
    • TLS via Let’s Encrypt / Certbot paths
    • Always test with nginx -t before reloading
    /etc/nginx/sites-available/example.com.conf
    
            

    Demo D · Disaster recovery

    Delete production. Then bring it back.

    A backup you haven’t restored is just a hope. Wipe the database, pick a snapshot and restore it — the drill measures how much data you’d lose and how long you’d be down.

    • Daily encrypted snapshots, 30-day retention
    • Point-in-time recovery from the write-ahead log
    • Restores tested on a schedule — not on the worst day
    postgres · shop_productionHealthy

    Snapshots · last 30 days

    Demo E · Server terminal

    SSH into a hardened box.

    A simulated shell on one of my standard servers. Look around, check the firewall and the containers — or run harden on a fresh machine and watch the checklist apply itself.

    Try: help · docker ps · ufw status · fail2ban-client status sshd · harden

    dan@prod-01: ~ (ssh · ed25519)Connected
    dan@prod-01:~$

    04 Architecture

    THE LIFE OF A REQUEST.

    Scroll down the stack. One click on your site travels through five layers — each one built, hardened and monitored.

    1. 01
      Edge & DNS

      Cloudflare DNS and CDN answer first: cached files are served from the nearest city, bad traffic is filtered before it reaches your server.

      Cloudflare · DNS · CDN · WAF
    2. 02
      Nginx

      TLS 1.3 termination, HTTP/2, compression and rate limiting — then the request is load-balanced across healthy containers.

      Nginx · Let's Encrypt · load balancing
    3. 03
      App containers

      Identical Docker containers run the app. One can crash or update while the others keep serving.

      Docker · Compose · health checks
    4. 04
      Data

      PostgreSQL for the records with replication, Redis for sessions, caching and rate-limit counters.

      PostgreSQL · Redis · pgbouncer
    5. 05
      Backups

      Encrypted daily snapshots and the write-ahead log go off-site — restores are tested, not assumed.

      pg_dump · WAL · off-site · 30 days

    05 Tech Stack

    BATTLE-TESTED TOOLS. NO SURPRISES.

    CategoryTechnologyUse CaseProfile
    OSUbuntu 22.04 LTSPrimary server OS — long-term support, extensive tooling, security patch pipelinePrimary
    Web ServerNginxReverse proxy, SSL termination, static file serving, load balancingPrimary
    DatabasePostgreSQL / MySQLRelational data with replication, automated backups, and connection poolingPrimary
    CacheRedisSession storage, rate limiting, pub/sub, and application-level cachingPrimary
    ContainersDocker + ComposeService isolation, reproducible environments, simplified deploymentStandard
    CI/CDGitHub ActionsAutomated testing, linting, build, and zero-downtime deployment pipelinesStandard
    MonitoringUptime Kuma / GrafanaService health checks, metric dashboards, alerting via Telegram/emailStandard
    SSLLet's Encrypt / CertbotAutomatic TLS certificate provisioning and renewal — zero manual workStandard

    06 Guarantees

    BUILT TO STAY ONLINE.

    My Uptime Commitment. Every deployment I maintain is monitored 24/7. Here's the uptime record across my managed services:

    0.9%Target Uptime

    Across all managed infrastructure deployments

    0hResponse SLA

    Critical incident response time for managed clients

    0sDowntime on Deploy

    Blue-green deployments — no interruptions to live traffic

    0%Automated Backups

    Daily snapshots with 30-day retention and restore testing

    Web Servers99.9%
    Databases99.97%
    APIs99.95%
    AI Services99.8%

    07 Process

    HOW I BUILD YOUR INFRASTRUCTURE.

    1. 01Audit & Requirements

      I review your current stack, traffic patterns, and growth projections to design an architecture sized for where you're actually headed.

    2. 02Server Provisioning

      VPS setup, OS hardening, user access, firewall rules, and fail2ban — secure out of the box.

    3. 03Application Deployment

      Docker configuration, Nginx setup, SSL, database initialisation, and application environment variables.

    4. 04CI/CD Pipeline

      GitHub Actions workflows for test, build, and deploy. Every push to main triggers an automated, zero-downtime deployment.

    5. 05Monitoring & Handoff

      Monitoring dashboards, alerting channels, runbook documentation, and a live walkthrough of everything I've built.

    08 Contact Open to full-stack roles · Dresden / remote

    Let’s build something
    people don’t log off from.

    Daanriddle@gmail.com