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.ts
- access.ts
- account-deletion.ts
- accounts.ts
- actions.ts
- advisories.ts
- agent-sessions.ts
- agents.ts
- audit.ts
- billing.ts
- chat-markdown.test.ts
- chat-markdown.ts
- chat.test.ts
- chat.ts
- checks.ts
- claude-plugin.test.ts
- claude-plugin.ts
- clients.ts
- codeowners.ts
- coding-agents.test.ts
- coding-agents.ts
- compute.ts
- connectors.test.ts
- connectors.ts
- customize.test.ts
- customize.ts
- d1.test.ts
- d1.ts
- datasets.fixtures.json
- datasets.test.ts
- datasets.ts
- deploy-keys.ts
- deployments.ts
- discovery.test.ts
- discovery.ts
- docs.ts
- events.ts
- folios-dashboard.ts
- folios-design.ts
- folios-slides.ts
- folios.fixtures.json
- folios.test.ts
- folios.ts
- github.ts
- guardrails.ts
- identity.ts
- ids.test.ts
- ids.ts
- inbox.ts
- index.ts
- instances.ts
- integrations.ts
- marketplace.test.ts
- marketplace.ts
- members.ts
- names.test.ts
- names.ts
- notify.ts
- oauth.ts
- og.ts
- packages.ts
- people.ts
- platform.ts
- projects.ts
- rate-limits.ts
- repos.ts
- result.ts
- rules.ts
- runners.ts
- scopes.ts
- search.ts
- security-suite.ts
- security.ts
- skills.ts
- sounds.ts
- status.ts
- teams.ts
- telemetry.ts
- updates.ts
- webhooks.ts
- work.ts