5 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
mathias	ef4e47bf00	ci: carry the shared build-image script (infra#309) ... Byte-identical copy of mathias/infra's ci-templates/build-image.sh, so repos generated from this template inherit a managed copy of one file rather than a private fork of the build logic.	2026-08-25 08:52:53 +00:00
mathias	bada904c8d	ci: build with buildctl instead of buildah (infra#241) ... Rootless buildah in gitea-runner's hardened securityContext (capabilities: drop [ALL], allowPrivilegeEscalation: false) cannot remap the UID/GID range newuidmap/newgidmap need on a fresh base-image pull, and the pod has no OCI runtime at all. buildctl talks to the host's buildkitd over a socket, so the privileged layer extraction happens on the host and the pod's securityContext stops being in the picture. Same pattern as mathias/infra's segment-embedder.yml. A template is the highest-leverage place to fix this: every repo generated from here inherits its CI, so a buildah-based template does not merely carry the bug, it manufactures new instances. The failure is latent — warm base-image layers mask it — so a generated repo builds fine until its first genuinely cold pull, which is precisely the situation a new repo is in. Verification is PARTIAL here, and the limit is worth stating rather than implying a green build. Running the exact command against this repo's real context reaches step 8 and fails inside the Dockerfile: RUN templ generate && go build ... -o /out/app ./cmd/__PROJECT_NAME__ error: failed to solve: ... exit code: 1 That failure is the template's own placeholder path, which cannot resolve on the raw template — the same reason the guard job gates check/build/deploy off here (is_template detects __MODULE_PATH__ in go.mod). What it does prove is that buildctl resolved the frontend, the context and the Dockerfile and began executing stages; every part of the buildctl integration worked, and only the template's unsubstituted content did not. template-go-agent's Dockerfile has no placeholder in its build path, so there the same command produced a complete 6.8MB OCI archive. The first generated repo from this template is where this one gets its end-to-end proof. skopeo copy replaces `buildah push` — buildctl has no registry-push equivalent — and runs twice to preserve the :sha and :latest tags.	2026-08-21 18:30:53 +02:00
mathiasandClaude Opus 4.8	8a22a28ab4	fix(template): parameterize scaffold with __PROJECT_NAME__/__MODULE_PATH__ (gitea-mcp#44) ... template-go-web was seeded from the real `hostexecutor` project and never parameterized: go.mod hardcoded `module gitea.d-ma.be/mathias/hostexecutor` and `hostexecutor` appeared throughout (cmd dir, Dockerfile, Taskfile, CI, context docs). create_project_from_template therefore substituted nothing and returned a "no placeholders" partial_failure on the zero-config default path. Replaced the full module path with __MODULE_PATH__ and the bare project name with __PROJECT_NAME__ (incl. renaming cmd/hostexecutor → cmd/__PROJECT_NAME__), matching the substitution the tool performs. Also drops the stale gitea.d-ma.be host (the placeholder resolves to git.d-ma.be/<owner>/<name>). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-07-03 23:33:46 +02:00
mathias	b2a87520b2	chore: drop environment: staging (no-op for solo homelab)	2026-05-05 08:51:20 +02:00
mathias	a25120cd1d	feat: initial template (Go + Templ + HTMX + CDN Tailwind)	2026-05-05 08:19:04 +02:00