Platform Summary
Hostnames and service boundaries
Why this matters
Each public hostname maps to one service boundary. That separation makes the platform easier to
deploy, monitor, secure, and explain under review.
| Hostname |
Purpose |
Target |
shellr.net |
Personal landing page and frontdoor |
Portfolio app container |
dma.shellr.net |
DMA application |
DMA PHP container |
grafana.shellr.net |
Metrics and logs UI |
Grafana behind Nginx auth |
status.shellr.net |
Uptime surface |
Uptime Kuma |
docs.shellr.net |
Static documentation |
GitHub Pages |
Start here
Review the architecture first, then the deployment path, then monitoring and backup. That sequence explains how the platform stays operable.
Open architecture
Case studies
Walk through concrete platform decisions with problem, constraints, implementation, and operational outcome.
Read case studies
Projects
Overview of the live platform, DMA, AWStats reporting, migration work, private hosting, and the planned vulnerability-management project.
Open project overview
Architecture
Routing, service boundaries, public vs. private surfaces, and why the platform remains intentionally single-host.
Review architecture
Monitoring and Logging
How metrics, uptime checks, alert rules, and short-retention logs provide visibility without turning the VM into an observability cluster.
Open monitoring details
Backup
What is backed up, what is excluded on purpose, how offsite sync is prepared, and how restore remains procedural under pressure.
Review backup strategy
Lessons Learned
Trade-offs that changed once the platform moved from planning to real services and real operational constraints.
Read lessons learned
Accessibility Review
Baseline checks for keyboard flow, focus visibility, mobile tables, and JavaScript fallbacks across the public surfaces.
Open accessibility review
Source of truth
The repo contains the same material as markdown under /docs for review and versioning.
Open docs source
Live surfaces
Jump directly from the documentation to the public platform, DMA workload, or the uptime surface.
Open status.shellr.net