Metrics and logs (restricted)
Marlin Scheler · Junior DevOps / System Engineer
Self-hosted platform demonstrating real-world system operation.
- Deployable through staged releases and health checks
- Observable through metrics, logs, and uptime tracking
- Recoverable through backups, restores, and rollback strategies
What you can do here:
- Explore the architecture
- View live system components
- Review operational decisions and trade-offs
Live System Components
Public entry points and restricted operations surfaces.
Platform Snapshot
Concrete operating characteristics of the platform.
Single Hetzner VM with 4 vCPU, 8 GB RAM, and bounded disk usage.
Services run in separate containers instead of sharing one unmanaged host setup.
Nginx handles HTTPS, redirects, and hostname-based routing for public services.
GitHub Actions deploys staged releases over SSH and checks service health before completion.
Prometheus, Grafana, Node Exporter, cAdvisor, and Uptime Kuma cover host and service visibility.
Database dumps, project archives, and restore scripts are part of normal operations.
Operational Metrics
Measured platform scope and operational coverage.
5 public hostnames routed through one ingress layer.
3 Docker networks separating frontend, backend, and monitoring traffic.
Daily database and runtime backup jobs with defined retention.
Host, container, and application checks are included in the stack.
Security Model
Security is treated as part of system design, not a side note.
Ingress Control
- TLS termination via Nginx (HTTPS only)
- Redirect enforcement and hostname routing
- Basic request filtering and rate limiting
Access Control
- Grafana and internal tools behind authentication
- No direct public exposure of internal services
Isolation
- Service separation via Docker networks
- Distinct boundaries between frontend, app, and monitoring
Recovery
- Regular backups with defined retention
- Restore scripts tested against real workloads
Operational Focus
This platform is designed to be operated, not just deployed.
- Incidents can be detected via metrics and uptime checks
- Logs provide traceability across services
- Deployments are gated by health checks
- Recovery paths are defined and tested
service map
one ingress layer, containerized services, monitored operations
Internet | Nginx (Ingress) | Docker Services (App / Monitoring) | Metrics + Logs (Prometheus / Grafana) | Backup System
Projects
Projects framed by concrete system behavior and operational value.
platform
Genesis / Self-Hosted Platform
Platform used to validate operational decisions under real conditions instead of theoretical setups.
- Focus: Deployability
- Focus: Observability
- Focus: Recoverability
- Linux
- Docker Compose
- Nginx
- GitHub Actions
live application
DMA Statistics Module
Simulates a stateful application to test deployment, monitoring, and recovery under realistic conditions.
- Includes: Database persistence
- Includes: Application runtime isolation
- Includes: Health-based monitoring and alerting
- PHP
- MariaDB
- Health checks
- Monitoring
reporting
Automated Web Analytics with AWStats
Generates lightweight reporting from webserver logs without adding a heavy analytics stack.
- Turns raw access logs into readable reports
- Runs on a scheduled shell-based workflow
- Fits the resource limits of a small single-host platform
- AWStats
- Shell scripts
- Cron
- Reporting
operations
Web Platform Migration and Hardening
Moves existing web workloads into a safer operating model with cleaner routing and tighter access control.
- Improves SSH, TLS, firewalling, and reverse proxy structure
- Reduces cross-impact between services
- Turns inherited setups into supportable systems
- Ubuntu
- SSH
- UFW
- Nginx
stateful application
Inventory Tracking Application
Simulates a stateful application to test deployment, monitoring, and recovery under realistic conditions.
- Includes: Database persistence
- Includes: Application runtime isolation
- Includes: Health-based monitoring and alerting
- PHP
- MariaDB
- CRUD
- Health checks
Documentation
Full documentation available: docs.shellr.net
The documentation site is the full technical record for the platform. It connects the landing page with architecture, deployment, monitoring, and recovery details.
Includes:
- Architecture
- Deployment flow
- Monitoring setup
- Backup and restore strategy