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
- ..
- about.rs
- activity.rs
- addresses.rs
- alerts.rs
- archives.rs
- audit.rs
- billing.rs
- blobs.rs
- broker.rs
- caches.rs
- checks.rs
- commits.rs
- contents.rs
- coordination.rs
- deploy_keys.rs
- deployments.rs
- folios.rs
- follow.rs
- lib.rs
- limits.rs
- logs.rs
- mcp.rs
- notifications.rs
- oauth.rs
- oidc.rs
- openapi.rs
- operations.rs
- packages.rs
- people.rs
- pins.rs
- projects.rs
- protection.rs
- reference.json
- renamed.rs
- responses.rs
- rest.rs
- rules.rs
- run_artifacts.rs
- runners.rs
- security.rs
- telemetry.rs
- token_policy.rs
- toolkit.rs
- tools.rs
- why.rs