Skip to content
View brockharries's full-sized avatar

Block or report brockharries

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
brockharries/README.md

Brock Harries

I've run a multi-million dollar restaurant end to end for eight years, and I built its web and ordering infrastructure, its network and its accounts myself, because there was nobody else to do it. Somewhere along the way the technology stopped being the chore and became the job I wanted.

These repos are my infrastructure, written up the way I'd explain a design to someone deciding whether to trust it: the problem, the design, the trade-offs, and what changes at scale.

  • ai-agent-engineering: how I directed AI coding agents to take a multiplayer game from an empty repo to working playtests in twelve days, with the method, the measured results and the failures
  • nextcloud-cloudflare-tunnel: a self-hosted platform publicly reachable with zero open inbound ports, threat model included
  • restaurant-web-infrastructure: the production stack that runs a real business, with the incident runbook and tested backups
  • vlan-segmented-network-security: a six-VLAN network with default-deny firewall policy and DNS as a security control

Also running at home: a four-node Proxmox cluster, monitoring that pages me, offsite backups, and a self-hosted AI assistant with retrieval over my own docs. I build most of the automation around it with AI coding tools, and I check their work against the live system before I trust it.

Find me on LinkedIn, or see the demo site at brockharries.dev, served from my own rack through the zero inbound ports design in the Nextcloud repo.

Pinned Loading

  1. nextcloud-cloudflare-tunnel nextcloud-cloudflare-tunnel Public

    Self-hosted Nextcloud exposed publicly with zero open inbound ports: Cloudflare Tunnel, TLS at edge, threat model included

  2. restaurant-web-infrastructure restaurant-web-infrastructure Public

    The production web and ordering stack behind a busy restaurant: edge/CDN, hardened origin, tested backups, incident runbook

    Shell

  3. vlan-segmented-network-security vlan-segmented-network-security Public

    Six-VLAN home network with default-deny firewall policy, DMZ isolation, and Pi-hole plus Unbound DNS as a security control

  4. ai-agent-engineering ai-agent-engineering Public

    How I directed AI coding agents to take a multiplayer game from an empty repo to working playtests in twelve days: briefs, decision records, tests, and a second model that can say no