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
- ..
- apache_airflow.yml
- argoproj_argo-cd.yml
- aws_aws-cdk.yml
- cli_cli.yml
- cloudflare_workers-sdk.yml
- dependabot_dependabot-core.yml
- docker_compose.yml
- electron_electron.yml
- every-option.yml
- getsentry_sentry.yml
- github_docs.yml
- hashicorp_terraform.yml
- hashicorp_vault.yml
- huggingface_transformers.yml
- microsoft_TypeScript.yml
- microsoft_vscode.yml
- nodejs_node.yml
- pypa_pip.yml
- python_cpython.yml
- pytorch_pytorch.yml
- supabase_supabase.yml
- tokio-rs_tokio.yml