Portainer's "Pull and redeploy" runs `compose pull` before `compose up`.
With `image: kaiser-natron:portainer` set, that tries to pull the image
from Docker Hub and fails with "pull access denied" because the image
only exists as a local build artifact. `pull_policy: build` tells
compose to skip the pull step for this service.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
The Portainer host keeps failing on `npm ci` inside the build stage
(both Alpine+libc6-compat and Debian slim exited 1 without ever surfacing
the real error to us). For a dev showcase this isn't worth chasing —
the dev machine is the source of truth for the built output anyway.
- Dockerfile: drop the Node build stage. Image is just nginx:1.27.3-alpine
with /dist copied in. No npm inside the container.
- docker-compose.yml: drop the production hardening (read_only, tmpfs,
security_opt, resource caps) and the container_name. Dev-only, don't
inhibit things.
- .gitignore / .dockerignore: stop ignoring dist/ — it's committed now.
- README: document the `npm run build && commit && push` release flow
and note what to reinstate when this graduates to real production.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
