Guides

Deployment

What changes when your app moves off localhost.

Two things change when you deploy: Clivly needs your real tick URL, and a serverless host needs somewhere durable to keep sync cursors.

Point the sync trigger at your deployed URL

While developing, clivly dev opens a tunnel and registers it for you. In production the URL is your own.

.env
CLIVLY_SYNC_TRIGGER_URL=https://yourdomain.com/api/clivly/tick

Confirm it took effect:

Package manager
terminal
npx clivly status

Persist cursors on serverless hosts

A long-running server can hold sync cursors in memory. A serverless function cannot — it is torn down between invocations, and a lost cursor means the next sync re-reads from the beginning.

Serverless hosts need a cursor store

On Vercel, Cloudflare Workers, Lambda, or any host that does not keep your process alive, configure cursorStore so sync resumes where it left off.

See Sync & cursors for the store interface.