README: fix heading case, reorder sections, split dense intro paragraph
- Heading capitalization consistent Title Case throughout - Moved the three personal sections (What I Have Explored, What I'm Focused On, Fun Fact) from between the two strongest technical sections to after Systems/What's Running, as a closing note - keeps momentum through the trust-boundary story into the diagram and full Systems breakdown, and gives the page a real closing beat instead of ending on a bare stack-count line - Split the dense opening bio paragraph into two at its natural seam
This commit is contained in:
1 file changed
+31
-33
@@ -1,4 +1,4 @@
|
||||
## About me
|
||||
## About Me
|
||||
|
||||
# 👋 Hi there — I'm @thesabear
|
||||
[](https://www.linkedin.com/in/michael-surgey)
|
||||
@@ -20,7 +20,9 @@
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
I'm a curious, self-taught technologist who runs a real, multi-host homelab as a production-grade playground. Most homelabs are a media server with some extra apps bolted on. This one is a platform: The same categories of systems a company's platform/security team owns, run at homelab scale, for real, 24/7, by one person. My long-term goal is to build a career in IT — specifically in environments where learning never stops and innovation is part of the culture.
|
||||
I'm a curious, self-taught technologist who runs a real, multi-host homelab as a production-grade playground. Most homelabs are a media server with some extra apps bolted on. This one is a platform: The same categories of systems a company's platform/security team owns, run at homelab scale, for real, 24/7, by one person.
|
||||
|
||||
My long-term goal is to build a career in IT — specifically in environments where learning never stops and innovation is part of the culture.
|
||||
What started as a hobby project has grown into a full-on journey into DevOps, automation, infrastructure, and security;
|
||||
|
||||
- <strong style="font-size:1.4em;">Proxmox</strong> — a hypervisor cluster running a fleet of hardened VMs/LXCs provisioned via Terraform
|
||||
@@ -45,35 +47,7 @@ The three routing authorities are also split across two separate physical nodes,
|
||||
|
||||
Full breakdown — the boundary-by-boundary reasoning, the routing-authority failure table, all 8 traffic laws: [docs/architecture-overview.md](docs/architecture-overview.md).
|
||||
|
||||
---
|
||||
|
||||
## 👀 What I Have Explored
|
||||
I use my homelab as a real-world playground to deepen my understanding of core IT concepts. Some of the areas I've learned and put into practice are:
|
||||
|
||||
- **Infrastructure-as-Code**: infrastructure that's provisioned, hardened, and reproducible from code — not clicked together by hand
|
||||
- **Security**: defense-in-depth in practice — network segmentation, secrets management, and identity, layered so no single control is ever the only thing standing between an attacker and everything else
|
||||
- **Automation**: fleet-wide operations running end-to-end on its own, with a human kept in the loop exactly where the consequences of getting it wrong are highest
|
||||
- **Monitoring**: observability and security detection working as one system, not two separate concerns bolted together
|
||||
|
||||
Each project started as something I didn't know how to do. Now it's just part of how this fleet runs — and pushes me further toward being a well-rounded IT/DevOps engineer.
|
||||
|
||||
---
|
||||
|
||||
## 🌱 What I'm Focused On Right Now
|
||||
|
||||
- Refining the Ansible roles and playbooks that keep the fleet patched and consistent
|
||||
- Looking for genuine opportunities to put my Gitea CI/CD to work beyond hosting the registry, wherever it'd actually help
|
||||
- Sharpening my scripting — Bash and Python, aimed at real-world IT skills I can use beyond this homelab
|
||||
|
||||
---
|
||||
|
||||
## ⚡ Fun Fact
|
||||
|
||||
I'm entirely self-taught. Every tool, trick, concept, and workflow in my repo's is something I learned by doing — from reading docs to breaking my lab at 2 a.m. and fixing it again before anyone noticed anything was ever wrong. There's no ticket queue here and no one to escalate to — when something breaks at midnight, I'm the on-call engineer, the incident commander, and the entire post-mortem team arguing with myself about whose fault it was (mine, always mine). I enjoy understanding not just how something works, but how to automate it, secure it, and integrate it cleanly into a larger system — "just add one more service" remains a permanent, unsolved architectural risk.
|
||||
|
||||
---
|
||||
|
||||
## Architecture At A Glance
|
||||
## Architecture at a Glance
|
||||
|
||||
|
||||
Solid arrows are hard dependencies — the target has to be reachable for the source to function. Dashed arrows are secondary relationships (request routing like "proxies"/"auth", or async telemetry reporting) that don't block the source if the target's unavailable. Full breakdown of all 8 traffic laws (ingress, east-west, secrets, DNS, observability, notifications, CI/CD, management) with the actual trust-boundary reasoning: [docs/architecture-overview.md](docs/architecture-overview.md).
|
||||
@@ -136,8 +110,32 @@ Docker images get built and hosted entirely in-fleet on the Git server's own bui
|
||||
Authentik, self-hosted, fronts single sign-on fleet-wide — native OIDC where an app supports it, proxy-based forward-auth covering everything else, so apps that were never built with SSO in mind still get it. Every OIDC login crosses reverse-proxy zones mid-handshake, and Git automation runs on a scoped bot account rather than an admin identity.
|
||||
→ [docs/sso-and-identity.md](docs/sso-and-identity.md)
|
||||
|
||||
## What's running
|
||||
## What's Running
|
||||
|
||||
53 Docker Compose stacks, grouped by purpose rather than by which host happens to run them — see [`stacks/`](stacks/): identity & security, platform/infra, media, productivity, and dev tools.
|
||||
|
||||
---
|
||||
---
|
||||
|
||||
## 👀 What I Have Explored
|
||||
I use my homelab as a real-world playground to deepen my understanding of core IT concepts. Some of the areas I've learned and put into practice are:
|
||||
|
||||
- **Infrastructure-as-Code**: infrastructure that's provisioned, hardened, and reproducible from code — not clicked together by hand
|
||||
- **Security**: defense-in-depth in practice — network segmentation, secrets management, and identity, layered so no single control is ever the only thing standing between an attacker and everything else
|
||||
- **Automation**: fleet-wide operations running end-to-end on its own, with a human kept in the loop exactly where the consequences of getting it wrong are highest
|
||||
- **Monitoring**: observability and security detection working as one system, not two separate concerns bolted together
|
||||
|
||||
Each project started as something I didn't know how to do. Now it's just part of how this fleet runs — and pushes me further toward being a well-rounded IT/DevOps engineer.
|
||||
|
||||
---
|
||||
|
||||
## 🌱 What I'm Focused On Right Now
|
||||
|
||||
- Refining the Ansible roles and playbooks that keep the fleet patched and consistent
|
||||
- Looking for genuine opportunities to put my Gitea CI/CD to work beyond hosting the registry, wherever it'd actually help
|
||||
- Sharpening my scripting — Bash and Python, aimed at real-world IT skills I can use beyond this homelab
|
||||
|
||||
---
|
||||
|
||||
## ⚡ Fun Fact
|
||||
|
||||
I'm entirely self-taught. Every tool, trick, concept, and workflow in my repo's is something I learned by doing — from reading docs to breaking my lab at 2 a.m. and fixing it again before anyone noticed anything was ever wrong. There's no ticket queue here and no one to escalate to — when something breaks at midnight, I'm the on-call engineer, the incident commander, and the entire post-mortem team arguing with myself about whose fault it was (mine, always mine). I enjoy understanding not just how something works, but how to automate it, secure it, and integrate it cleanly into a larger system — "just add one more service" remains a permanent, unsolved architectural risk.
|
||||
Reference in new issue
Block a user