Deployment

Acme Platform provides a fully managed deployment pipeline with automatic builds, preview environments, and zero-downtime rolling updates. This guide covers the most common deployment workflows.

Deploy via CLI

1. Build your project locally (optional — Acme can build remotely too):

   npm run build

2. Deploy to production:

   acme deploy --production

3. Verify the deployment:

   acme status

Preview Environments

Every pull request can automatically receive a preview deployment. Enable this in your project settings or deploy manually:

acme deploy --preview

Preview URLs follow the pattern https://<branch>--<project>.preview.acme-platform.com.

Deployment Targets

Cloudflare Workers

Acme Platform deploys to Cloudflare Workers by default. Edge-deployed functions run in 300+ locations worldwide with sub-millisecond cold starts.

Docker

For containerized workloads, export a Dockerfile and deploy to any container registry:

acme export --format docker
docker build -t my-app .

Static

Static sites are deployed to a global CDN with automatic cache invalidation on each deploy.

Tip

Set up a acme.config.json in your project root to configure build commands, environment variables, and deployment targets declaratively.

Rollbacks

If a deployment introduces a regression, roll back to the previous version instantly:

acme rollback --production

Next Steps

Read the Configuration guide to learn how to manage environment variables and feature flags across environments.