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
- ..
- deploy
- emoji
- ops
- perf
- apt-install.sh
- build-runner.mjs
- build-rust-worker.mjs
- cli-release.mjs
- cli-release.test.mjs
- cloudflare-setup.py
- conformance-diff.mjs
- deploy.mjs
- deploy.sh
- desktop-cross-tools.sh
- desktop-release.mjs
- desktop-release.test.mjs
- mobile-release.mjs
- mobile-release.test.mjs
- runner-release.mjs
- runner-release.test.mjs
- sandbox-image.mjs
- sccache.sh
- setup-custom-domains.sh
- setup-deployments.sh