syntaqxA project with a site and a Dockerfile deploys as a container when the Dockerfile runs a server (CMD, ENTRYPOINT, or EXPOSE on an image that is not only a file server), and as the site otherwise, and the build's log says which and why; before, any framework that builds a site ignored the Dockerfile, so a Vite front end with its own server lost its back end, and a bare index.html beside an nginx Dockerfile asked for a container. A Dockerfile's port is its EXPOSE, else the PORT it sets with ENV; Next.js's standalone output runs its own server.js; Rust servers on axum, actix-web and the like get a Dockerfile; images are built without a provenance attestation, as wrangler builds them, so the digest pushed is the image's own; and the messages that said g1t.page runs no servers say what to change instead.4ee36edHistory
- ..
- backup.test.ts
- backup.ts
- broker-egress.ts
- broker-relay.test.ts
- broker-relay.ts
- broker.test.ts
- broker.ts
- bump.test.ts
- bump.ts
- credentials.test.ts
- credentials.ts
- egress.test.ts
- egress.ts
- forward.test.ts
- forward.ts
- gate.test.ts
- guard.ts
- index.ts
- lifecycle.test.ts
- lifecycle.ts
- machines.test.ts
- self-hosted.test.ts
- self-hosted.ts