Add TFGrid single-VM deployment with web gateway (HTTPS) #41

New issue

Open

opened 2026-02-27 00:25:13 +00:00 by mik-tf · 0 comments

mik-tf commented

2026-02-27 00:25:13 +00:00

Owner

Problem

Hero OS has a working production Docker container but no deployment automation for TFGrid.

Solution

Add deploy/single-vm/ following the established pattern (hero_books, marketplace):

OpenTofu config with grid_name_proxy for HTTPS via TFGrid web gateway (no public IPv4 needed)
setup.sh — install Docker, pull container, run with zinit auto-restart
update.sh — quick pull + restart
Makefile — ENV=prod|dev multi-environment orchestration
envs/ — per-environment config (prod/dev)

Gateway handles SSL termination automatically. Container exposes Hero OS on internal port, gateway proxies HTTPS traffic over WireGuard.

Container

forge.ourworld.tf/lhumina_code/hero_zero:latest — pre-built production image with all services.

## Problem Hero OS has a working production Docker container but no deployment automation for TFGrid. ## Solution Add `deploy/single-vm/` following the established pattern (hero_books, marketplace): - **OpenTofu** config with `grid_name_proxy` for HTTPS via TFGrid web gateway (no public IPv4 needed) - **setup.sh** — install Docker, pull container, run with zinit auto-restart - **update.sh** — quick pull + restart - **Makefile** — `ENV=prod|dev` multi-environment orchestration - **envs/** — per-environment config (prod/dev) Gateway handles SSL termination automatically. Container exposes Hero OS on internal port, gateway proxies HTTPS traffic over WireGuard. ## Container `forge.ourworld.tf/lhumina_code/hero_zero:latest` — pre-built production image with all services.