7 Commits

Author SHA1 Message Date
jason 520119f65b ci: unify to canonical docker-build workflow (drift labels baked in)
Build and Push Docker Image / build (push) Successful in 3m25s
2026-07-19 13:37:19 -05:00
Jason Stedwell d35339f75b ci: trigger PORT auto-redeploy after image push
Build and Push Docker Image / build (push) Successful in 1m3s
2026-07-18 20:25:30 -05:00
jason 0cd1d6375d Point docker-build.yml trigger at main
Build and Push Docker Image / build (push) Has been cancelled
2026-07-02 10:16:40 -05:00
jason 429cd655ec Update docker-build.yml workflow
Build and Push Docker Image / build (push) Successful in 51s
2026-07-02 10:03:17 -05:00
Jason Stedwell 39c4d0933e Drop BuildKit cache mounts so legacy builder can build the image
Build and Push Docker Image / build (push) Successful in 3m1s
The host runner's Docker CLI forces the buildx path when DOCKER_BUILDKIT=1
is set, but buildx isn't installed on the runner, so the build errored
before starting. Revert the env var and remove the two RUN --mount=type=cache
directives so the legacy builder can parse the Dockerfile. Normal layer
caching still applies; only the npm download cache reuse is lost.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-30 09:06:52 -05:00
Jason Stedwell 4958480d6f Enable BuildKit for docker build in CI
Build and Push Docker Image / build (push) Failing after 2s
The host runner's docker build was falling back to the legacy builder,
which can't parse the BuildKit-only RUN --mount=type=cache syntax in the
Dockerfile. Set DOCKER_BUILDKIT=1 to route the build through the daemon's
integrated BuildKit engine.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-30 09:04:30 -05:00
jason 3ec35ec095 Add docker-build.yml: build + push :latest to registry.alwisp.com on the host runner
Build and Push Docker Image / build (push) Failing after 3s
2026-06-30 07:36:58 -05:00