Back to projects

mDeploy: Estate Deployment & Architectural Parity

An automated release pipeline and governance engine enforcing strict architectural standards, secrets safety, and deterministic deployment workflows across multi-service private repositories.

Role
Architect & Developer
Scope
10+ Estate Repositories (Mobile, Systems, Services)
Timeline
2026
Stack
TypeScript, Node.js, PowerShell, Docker, GitHub Actions
Codebase
Private (Active HomeLab infrastructure)

The problem

Operating a diverse homelab estate composed of Android mobile apps, Go daemons, Rust native binaries, and Python workers inevitably leads to architectural drift. Over time, repositories end up with inconsistent documentation structures, missing secrets templates, out-of-sync CI configurations, and manual deployment steps that introduce human error during updates.

What I built

I engineered mDeploy together with a repository scaffolding engine to treat developer tooling and architecture as code. It provides an automated verification harness that audits every repository for strict file layout compliance (verifying all 33 required standard files), runs type-checked build scripts (tsc -b), checks git tree health, and orchestrates atomic deployments to target hosts.

Architecture

┌────────────────────────────────────────────────────────┐
│           Developer Workspace & Pre-Commit Hook        │
└───────────────────────────┬────────────────────────────┘
                            │ CLI Invocation / CI Trigger
┌───────────────────────────▼────────────────────────────┐
│                  mDeploy Engine (TypeScript)           │
│  ├── Compliance Validator (33/33 Standard Layout)      │
│  ├── Secrets Scanner (.env.secrets.example validation) │
│  ├── Type Checker & Test Runner (tsc / go test)        │
│  └── Container & Service Release Orchestrator          │
└───────────────────────────┬────────────────────────────┘
                            │ Target Dispatch
             ┌──────────────┴──────────────┐
             ▼                             ▼
    Local Docker Daemons          Cloudflare / Edge Services

Engineering challenges & trade-offs

Balancing strict repository governance with developer velocity was the central design challenge. Rather than imposing rigid, heavyweight enterprise frameworks, mDeploy relies on fast, localized CLI checks (such as scaffold.ps1 -Check) that report pass/fail status in milliseconds. This catches configuration gaps before code ever reaches deployment.

Key takeaways

Standardizing repository architecture is one of the highest-leverage investments in a homelab. With mDeploy, every project shares identical runbooks, development guides, and deployment conventions, reducing context switching and eliminating deployment surprises.

See other projects