Overview - Twenty — ContextQMD

The operations layer is everything you do to your app rather than with it: invoking CLI commands, running integration tests against a real Twenty server, configuring CI, and shipping releases — either as a tarball deployed to a single server or as an npm package listed in the marketplace.

text

   develop ─▶ test ─▶ build ─▶ deploy / publish
   ───────    ────    ─────    ─────────────────
   yarn       yarn    yarn     yarn twenty deploy   (tarball → one server)
   twenty     test    twenty
   dev                build    yarn twenty publish  (npm → marketplace)

In this section

<CardGroup cols={2}> <Card title="CLI" icon="terminal" href="/developers/extend/apps/operations/cli"> `yarn twenty` reference — exec, logs, uninstall, remotes. </Card> <Card title="Testing" icon="flask" href="/developers/extend/apps/operations/testing"> Vitest setup, integration tests, type checking, CI workflow. </Card> <Card title="Publishing" icon="upload" href="/developers/extend/apps/operations/publishing"> Build, deploy a tarball, publish to npm, install. </Card> </CardGroup>