Deploy and claim

Deploy without an account

npx coline-app deploy

The CLI builds the site and the app's logic, uploads them, and prints the address and a claim link. Nothing else is needed: no account, key or login.

• The address is the app key plus a random suffix, such as guestbook-k96h-c24658.coline.space.
• The site stays up for 72 hours after its last deploy, then it's deleted.
• .coline/site.json keeps the site's deploy token, so later deploys from the same folder update the same site. The folder is ignored by git.
• The page shows a small "Deployed on Coline" badge, and search engines are asked not to index it.
• It can use only what's scoped to the site itself. See limits.

Claim a site

Open the claim link (also in .coline/site.json, or run npx coline-app claim), sign in, and pick a workspace. The claim page lists what the site will be able to do in that workspace. Claiming moves the app, its records, visitors and logs into that workspace, and:

• the site gets the rest of the permissions it declares, such as seeing members, sending notifications, endpoints or Coline AI;
• the site stops expiring and the badge goes away;
• search engines may index it;
• the deploy token stops working: deploy with a workspace API key from then on.

An admin can turn any of those permissions off later under Apps → Your apps → Manage.

Deploy into a workspace

With a workspace API key that has apps.write, the site goes straight into that workspace and never expires:

export COLINE_API_KEY=col_ws_...
npx coline-app deploy --name my-site     # my-site.coline.space

--name picks the address on the first deploy. Reserved and taken names fail with SITE_SLUG_TAKEN or SITE_SLUG_INVALID.

Coline Code projects deploy the same way: create a project from the Site template and press Deploy. Kairo can build and deploy a site for you from chat.

Redeploy

Run deploy again from the same folder. The version comes from package.json; with 0.0.0 or none, each deploy gets its own. Redeploying the same version with different files fails with SITE_VERSION_EXISTS; bump the version. A redeploy is live within seconds, and pages that were already open keep working.

In Coline

A claimed site is an installed app in its workspace:

• Apps → Your apps lists it with the site's favicon. Open shows the app's home, or the site's address if it has none.
• Manage rolls back to any earlier version, turns automatic updates on or off, and turns permissions on or off. Turning off Public website takes the site offline until it's turned back on.
• Uninstall takes the site offline and keeps its data for 30 days. Reinstalling brings it back. Uninstall and delete data deletes the site, its visitors, files and custom domains.
• The developer console's Site settings rename the address, list, approve and manage visitors, manage files, and connect custom domains.

Local development

npm run dev runs the site at http://127.0.0.1:3000 with in-memory data and the same rules as Coline: collection rules, schemas, access modes, uploads and endpoints. Sign-in is simulated. Add ?as=alice to any URL to be a signed-in visitor named alice, ?as=guest for a new guest; two browser profiles are two visitors. Editing the page keeps local data; editing app.config.ts or the server code it imports resets it. Files that aren't source, such as screenshots, don't trigger a rebuild.

CLI

logs, db dump and db export read a running dev server with --port. sites delete with a deploy token deletes an unclaimed site and its app; with a workspace key it deletes the site, its visitors and files, and keeps the app and its records. Every command takes --json and prints { ok: true, data } or { ok: false, error: { code, message, fix } }.

Exit codes: 0 ok, 1 error, 2 needs sign-in or a claim, 3 over a limit.