cimplify
CLI

Deploys & projects

Create a project, link your CWD to it, and ship. Every deploy is a git SHA + a build; rollbacks are just re-deploys of an older SHA.

Projects

# List projects in the linked business
cimplify projects ls

# Create a new project
cimplify projects create my-store

# Link CWD to a project
cimplify link <project-id>
# Writes .cimplify/project.json (commit this file).

# Unlink
cimplify unlink

Linking writes .cimplify/project.json in the current directory. The file contains the project ID and the linked business; commit it so every developer / CI run deploys to the same project.

Deploy

# Preview deploy of the current branch HEAD
cimplify deploy

# Promote to production
cimplify deploy --prod

# Deploy a specific SHA (must already exist on the remote)
cimplify deploy --ref 3f9a2b1 --no-push

# Don't wait for the build (fire and forget)
cimplify deploy --no-poll

Flags

FlagDescription
--prodDeploy to production. Default is preview.
--ref <sha>Override the git ref. Defaults to HEAD of the current branch.
--no-pushSkip git push. Assumes the remote already has the SHA.
--allow-dirtySkip the dirty-tree confirmation prompt.
--no-pollReturn after enqueue; don't stream build progress.

By default cimplify deploy pushes the current branch to the remote, enqueues a build, and streams its progress until the build terminates. The exit code reflects the build's terminal status.

Rollback

# List recent deploys
cimplify status

# Re-deploy a previous deployment's SHA
cimplify rollback dpl_a1b2c3d4

rollback takes a deployment ID, not a SHA. It enqueues a fresh build of the same SHA so you can roll forward again later if you need to.

Status & logs

# Latest deployment + state for the linked project
cimplify status

# Stream logs for the latest deployment
cimplify logs --follow

# Or scope to a specific deployment
cimplify logs --deployment dpl_a1b2c3d4

Logs flags

FlagDescription
--deployment <id>Override which deployment to read. Defaults to the latest.
--followPoll until the deployment terminates.

dev with remote env

Run your project's dev script with the production env scope wired in. Useful for sanity-checking config drift before a production deploy.

# Local dev with local .env.local
cimplify dev

# Local dev with production env vars
cimplify dev --remote

Typical workflow

From PR to production
# Working on a feature branch
cimplify deploy                      # preview deploy from HEAD

# After review: ship
git checkout main && git pull
cimplify deploy --prod

# Something broke; roll back
cimplify status                      # find the previous good deploy
cimplify rollback dpl_<previous-id>

# Triage with logs
cimplify logs --deployment dpl_<bad-id> --follow

Where next

On this page