Environments & deployment

Start with local development. The current release is a source preview, not a production-ready checkout.

What runs in your account

• One Worker per environment serves the API and connects your systems.
• Durable Objects keep Cart, payment and Order state.
• D1 can provide the Order list. It is a projection, not the source of truth.
• Your storefront runs wherever you choose. Only the commerce runtime needs Cloudflare.

Test and live are separate environments with separate keys. A Channel defines a currency and selling rules inside an environment; it is not an environment.

The current deployment path

Deployment is manual today, using Wrangler. There is no orbcart deploy command yet. The concrete reference is examples/nordgrat/README.md, section Deploy to test, alongside its wrangler.jsonc.

A test deployment needs:

1. The merchant's connected systems.
2. The commerce Worker and its Durable Object bindings.
3. D1 migrations if you enable the Order list.
4. A root secret and the provider's test credentials, stored as Worker secrets.
5. Provider webhook endpoints pointing at the environment.
6. OrbCart keys for the storefront and its allowed browser origin.

Don't copy Nordgrat's Worker names, database IDs or domains into a different merchant's account. Keep live credentials out of the demo.

Before real purchases

Legal texts, confirmation emails and the final buyer Order page still need to be completed. Provider setup, access controls and your operational recovery process also need verification for your environment.

The project status distinguishes what exists from what is still being built. A running test checkout is not a production-readiness guarantee.