Skip to main content

Getting started from a local codebase (kapi)

The kapi developer path: connect a local project to your Bowrain server, push the source for the team to translate, and pull translations back — synced like git. This is one of several routes into a workspace, and the one for a developer working from a checkout. Content in a content platform, a design tool, or a repository connects server-side instead — no checkout, and nothing installed.

Outdated wording

The narration uses terminology that has since been retired. The interface and the behaviour shown are unchanged.

kapi init --server https://app.bowrain.cloud writes a kapi.yaml recipe and a sibling .kapi/ state directory and connects the project to your Bowrain server (pass --workspace <slug> if you belong to several). kapi add tracks the files you want translated; kapi push sends the source up (pure transport); kapi status shows standing, exactly like git; and kapi pull brings translations back into the same files and formats. kapi up does all of it on the server in one command — push, catch up, and pull — for the daily reconcile and for CI.

Next​