Containers healthy
Senior Engineering Build
This build sits above the live hosting stack and focuses on governance, observability, incident response, deployment control, backup verification, security posture, and business workflow traceability.
Hosting model: this portfolio page lives on GitHub Pages, while the live application runtime is hosted on the UpCloud VPS.
Example operational snapshot: values below are demonstration records showing how the control plane presents live telemetry and service state.
Containers healthy
7-day service uptime
Median API response latency
Last unplanned restart window
| Service | Status | Uptime | Last Restart | Dependency Check | Notes |
|---|---|---|---|---|---|
| Paymenter | Online | 99.91% | 2026-06-01 04:22 | MariaDB + Redis reachable | Billing API healthy |
| Nginx Proxy Manager | Online | 99.98% | 2026-05-29 01:11 | SSL renew queue clear | Host routes valid |
| Discord Bot | Degraded | 99.72% | 2026-06-04 22:05 | Gateway reconnect spikes | Reconnect policy tuning pending |
| Nextdactyl Integration | Online | 99.88% | 2026-05-31 03:44 | Panel API auth valid | Provisioning queue stable |
Sample incident record: illustrates severity handling, timeline tracking, and postmortem capture format.
Incident: Paymenter unavailable
Severity: High
Affected: billing portal, customer invoices, provisioning flow
Detected by: synthetic health check + container liveness alert
Demonstration ledger entries: format for change governance, rollback visibility, and migration risk tracking.
| Date | Change | Commit | Affected Services | Migration | Rollback | Result |
|---|---|---|---|---|---|---|
| 2026-06-05 | Health-check worker retry policy update | f7c3a4d | ops-control-worker, paymenter-monitor | No | Yes | Success |
| 2026-06-03 | Discord event ingest queue tuning | 8ea2b11 | skyhigh-bot, ops-control-api | No | Yes | Success |
| 2026-05-31 | Billing event webhook schema update | 1ac68de | paymenter, ops-control-api | Yes | Yes | Monitored |
Sample backup panel: demonstrates restore-test reporting, retention policy display, and encryption status tracking.
Successful
Last backup: 2026-06-05 03:00 UTC
Restore test: Passed
Retention: 7 daily / 4 weekly / 3 monthly
Encryption: Enabled
Successful
Last backup: 2026-06-05 03:05 UTC
Restore test: Passed
Checksum verification: Valid
Watch Backup size delta threshold enabled
Failure alert channel: Discord + email
Escalation path: on-call + incident board
Restricted Admin paths limited via firewall + routing rules.
Enabled Protected routes and scoped tokens configured.
Mapped Internal services not exposed directly.
Due in 12d API key rotation reminder active.
Reason: faster delivery, lower operational burden, better fit for current scale. Tradeoff: lower native autoscaling. Future path: migrate critical services to k3s/managed Kubernetes when utilization warrants.
Reason: host-based routing speed and operational usability. Tradeoff: less dynamic than Traefik-native discovery. Future path: move to Traefik if service churn increases.
Read-only service health, uptime, SSL/domain and connectivity checks.
Incident management and deployment ledger with rollback visibility.
Backup verification, restore testing records, and security exposure dashboards.
Business workflow observability for billing, provisioning, and Discord operations.
Case-study evidence pack with architecture diagrams, screenshots, and outcomes.