Deploys & projects

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.

Connecting a git repo

Every project deploys from a git repo. Cimplify builds the exact commit you push, so the project needs a remote to push to. You have two options.

Managed repo (recommended). Cimplify hosts the repo for you on its managed Git host. Provision one:

cimplify repo provision

With a managed repo, cimplify deploy mints a short-lived push token and pushes for you; you don't configure origin yourself.

Bring your own repo. Connect an existing GitHub/Gitea/external remote:

cimplify repo connect https://github.com/you/store.git
git remote add origin https://github.com/you/store.git

For connected repos, cimplify deploy runs a plain git push origin <branch> using your existing git auth, so origin must be set.

Inspect what's attached at any time:

cimplify repo info        # provider, remote_url, default branch, last pushed
cimplify repo clone-url   # print a fresh authenticated push URL (managed repos)

Troubleshooting: if cimplify deploy fails with git push origin <branch> failed: 'origin' does not appear to be a git repository, the project has no repo wired. Run cimplify repo provision for a managed repo, or cimplify repo connect <url> + git remote add origin <url> for your own. Do not point origin at an unrelated GitHub repo; managed-repo builds clone from Cimplify's host, not GitHub, so the push would land somewhere the build never reads.

The project's default branch is set at creation (usually main). Match your local branch to it before the first deploy:

git branch -M main

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

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

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

# 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

• env push, pull, scopes.

• domains Add, verify, attach, primary.

• login Browser-first PKCE.

• CLI overview Full index.