Preview & production

cellp selects the target version with HTTP Host. Gateway forwards the request path unchanged from /. Deprecated path selectors and WebSocket behavior: Gateway routing.

Preview

Preview Host (synthetic FQDN):

{version}.{project}.{base-domain}

Default base domain: ingress.local (CELLP_INGRESS_BASE_DOMAIN).

Example:

GET http://v-abc123.demo-app.ingress.local:8787/…

The API returns preview_url when you create a version; after deploy it matches the Host binding (includes :8787 in dev when Gateway is not on port 80/443).

GET /v1/projects/{id} exposes prod_url for the stable production Host. Until the first version is ready, prod may be unset; the first ready version is assigned production automatically (Projects).

Production

GET http://{project}.{base-domain}:8787/…

Example: http://demo-app.ingress.local:8787/ → current prod_version_id.

On a new project, the first version that reaches ready is assigned production automatically (see above). Later production changes are explicit promote cutovers. Promote does not change the prod Host—only which version backs it.

What preview is for

Because child versions branch data, preview is a real environment:

• Checkout on a PR version writes orders into that D1 branch
• KV banners you tweak in preview do not appear on prod Host
• You can keep a long-lived v-staging pinned and fork PRs from it

Data snapshot timeline

Preview is not “live production plus your PR code.” When you set parent_version_id, cellp forks data bindings (D1, KV, R2, Queue) from that parent during deploy. The child sees the parent celld bucket as it was at fork_txid (D1’s branch cut point). Writes on the parent after the child is created stay on the parent bucket — the preview does not see them.

Typical PR flow: parent = a pinned staging or seed version, not ad-hoc live prod. Production is still its own version and bucket; prod Host traffic does not stream into preview.

Cron on preview

Whether a ready version runs scheduled handlers depends on the production pointer (full policy: Cron).

• prod_version_id empty — any version that deploys ready may arm cron, including traffic on preview Hosts. The first ready version is usually assigned production automatically soon after.
• prod_version_id set — only the production version arms cron; other ready preview Hosts do not run scheduled.

After promote, only the new production version arms cron.

Local dev (hosts & LAN)

Contributor stacks: dev/INGRESS-HOST.md (unified guide).

Mode	Setup
Default	CELLP_INGRESS_BASE_DOMAIN=ingress.local + /etc/hosts → 127.0.0.1
LAN (no per-client hosts)	./dev/scripts/ingress-host-init.sh magic (nip.io / sslip.io)
Clash / system proxy	dev/clash/README.md — nip.io needs DIRECT or browser 502

Quick init:

./dev/scripts/ingress-host-init.sh local   # or magic
./dev/scripts/reset.sh && ./dev/scripts/up.sh && ./dev/scripts/seed-demo.sh

Example /etc/hosts (local):

127.0.0.1 v1.demo-app.ingress.local demo-app.ingress.local

Probe without editing hosts:

curl -H "Host: v1.demo-app.ingress.local" http://127.0.0.1:8787/
curl -H "Host: demo-app.ingress.local" http://127.0.0.1:8787/health

Always use http:// and include :8787 in the browser unless TLS terminates on an outer proxy.

Contributor normative design: INGRESS-ROUTING.md.