Project / Barndoor
Information refreshed August 16, 2026Barndoor is my self-hosted infrastructure and AI operations platform. A bare-metal Linux server remains the central control plane for local AI, Discord applications, public websites, monitoring, Minecraft, power telemetry, recovery evidence, and authenticated Raspberry Pi edge nodes.
Barndoor began as one self-hosted server and has grown into a coordinated platform. GitHub holds the clean source of truth, the main host runs the control plane, public and Discord surfaces expose bounded capability, and dedicated Raspberry Pis display or report health without becoming alternate administration systems.
The platform favors small components with explicit roles: system services, Docker workloads, static websites, local JSON APIs, source-controlled scripts, focused contract tests, preview-first deployment, rollback evidence, and documentation that stays close to the systems it describes.
Central Control Plane Source of Truth Public-Safe Telemetry Selective Deployment Documented RecoveryLayer 1
The repository contains bot code, agents, websites, appliance source, infrastructure templates, runbooks, checks, and deployment helpers. Pull requests and the unified release gate protect the platform before live changes.
GitCIContractsDry RunsLayer 2
The main Ubuntu Server host runs the Barndoor assistant, local AI, supporting agents, APIs, maintenance, backup tooling, and host-side health collection through a deliberate systemd and Docker runtime model.
Ubuntu ServersystemdDockerOllamaLayer 3
Caddy and application services host project sites, Barndoor Engineering, Haystack, Minecraft, monitoring, the full NOC, and bounded public APIs. Source editing and live deployment remain separate.
CaddyWebsitesDiscord AppsPublic APIsLayer 4
A Raspberry Pi 5 runs the permanent 800×480 touchscreen NOC. A Raspberry Pi Zero reports signed apartment-edge health over the private network with freshness, replay, source, and public-output controls.
Pi 5 NOCPi Zero EdgeSigned ReportsRead-Only UIA service registry, modular collectors, active-versus-resolved events, typed recovery evidence, and bounded APIs provide one health model across Discord, the NOC, scripts, and appliances.
Service RegistryEvent TimelineRecovery EvidenceThe full NOC supports deep diagnostics and history. The Pi wallboard provides persistent touch-first health, service details, recent events, bounded logs, and quick tools.
Open the full NOC →
Open the Pi wallboard →
Signed reports carry node checks, uptime, temperature, and network signal into the shared health model. Operations classify healthy, stale, failed, critical, malformed, and recovered states.
FreshnessReplay ProtectionBounded StorageLocal language models support question answering, summarization, explanations, project assistance, and model controls through the Barndoor Discord app without exposing the model runtime publicly.
OllamaLocal ModelsPrivate RuntimeThe main Barndoor assistant and separate source-controlled agents provide owner operations, Minecraft community features, Haystack financial simulations, and the 9eo music experience.
Barndoor BotMinecraft AgentHaystack9eoBarndoor hosts tylerrodgers.space, TM44.link, Barndoor Engineering, project pages, both NOC surfaces, and the generated Build Log through a shared Caddy-based web layer.
Static SitesBarndoor EngineeringBuild LogThe Paper server, Java and Bedrock access, BlueMap, Discord bridge, player tools, verified full backups, player-aware snapshots, bounded logs, and restore drills are managed as one guarded service.
PaperBedrock BridgeBlueMapBackupsNetwork UPS Tools data powers owner reports, public-safe API summaries, and transition-based events for power loss, low battery, bypass, shutdown, restoration, and query recovery.
UPSNUTPower EventsRuntime Doctor, the concise bdops dashboard, maintenance audits, source/live drift checks, SMART validation, bounded event retention, website contracts, backup verification, and restore drills turn routine operations into repeatable evidence instead of optimistic assumptions.
Deployments begin with a clean synchronized source baseline, pass focused and unified checks, preview the exact copy, back up the affected live target, and verify health or public behavior afterward. Live folders remain separate from the clean source repository.
Fail ClosedRuntime DoctorDrift ChecksSMARTRestore DrillsRollbackThe first card is synchronized automatically from the public Build Log.
Latest verified milestone
The touch wallboard now reconciles platform checks, opens service and event detail, exposes bounded local observations, and includes SMART, Moonwatch, and Market Pulse quick tools.
Pi NOCTouchscreenService IntelligenceBlocking restart, readiness, syntax, smoke, and final-health failures can no longer end with a false green result. Read-only storage, package, process, log, backup, and SMART audits provide pre-change evidence.
MaintenanceGuardrailsSMARTThe homepage, Now page, Barndoor overview, Barndoor Engineering product site, Haystack page, and TM44 hub now describe the same current platform and product boundaries.
DocumentationPublic SitesSource of TruthBarndoor’s major foundations are in place. Current work is focused on making the existing platform easier to understand, verify, restore, and extend safely.