Environments and deploy

Workers deploy with Wrangler targets deploy-dev / deploy-staging / main. This docs site deploys from Cloudflare Pages on main.

No secrets, tokens, connection strings, or example API keys belong in these pages.

Event Worker hosts (verified)

eventlinx-api-event is the ticketing system of record:

Environment	Host
Production	https://api-event.eventlinx.com
Staging	https://api-event-staging.eventlinx.com
Dev	https://api-event-dev.eventlinx.com

OpenAPI is served by the Worker: GET /doc. The spec is generated from src/routes.ts in eventlinx-api-event. Event authenticates callers with header X-API-Key (env EVENT_API_KEY). There is no end-user session on Event.

Do not paste keys into docs or curl examples. Use a local secret manager / Wrangler secrets.

Other services

Patron, promoter, GO, Stripe, authentication, and seating-detect follow the same Wrangler dev / staging / main pattern. Exact public hostnames for those BFFs are not copied here — they live in each repo’s Wrangler config. Do not assume they share the api-event-* hostname shape.

Docs site

Item	Value
Repo	eventlinx-dev-docs
Public URL	https://devdocs.eventlinx.com
Hosting	Cloudflare Pages
Deploy branch	main

Local preview:

yarn
yarn start

Production build:

yarn build
# or
yarn cloudflare-build

Pages publishes the build/ output. Feature branches do not go live until merged to main.

What not to put in this repo

• Wrangler / Cloudflare API tokens
• EVENT_API_KEY or any BFF service key
• Supabase URL, anon key, or service role
• Database URLs
• Example keys (including legacy Petstore special-key)
• Copied PCI / IRP / compliance pages (those stay on client docs)

If a runbook needs a secret name, write the name only (EVENT_API_KEY), never a value.