Skip to content

Document CLI V2#364

Open
benitav wants to merge 17 commits intomainfrom
cli-v2
Open

Document CLI V2#364
benitav wants to merge 17 commits intomainfrom
cli-v2

Conversation

@benitav
Copy link
Collaborator

@benitav benitav commented Feb 23, 2026

i.e. the implementation of https://docs.google.com/document/d/1iqpJF2gog2jB-ZWeN8TBEjcad8aBKNKbue2yJ21q_-s/edit

TODOS:

  • Publish the new repo publically and update Github file references in these docs accordingly (current ones assume the cli will be published as powersync-ja/powersync-cli)
  • Publish to NPM
  • Insert minor version number of the NPM package

* Generate the [client-side schema](/intro/setup-guide#define-your-client-side-schema)
**Cloud:** Full support for PowerSync Cloud. Log in with a personal access token, then define your instance config in a `powersync/` directory (`service.yaml`, `sync-config.yaml`) in your project and deploy with `powersync deploy`.

**Self-hosted:** You can link to an existing PowerSync Service instance and run a subset of commands (e.g. `powersync status`, `powersync generate schema`, `powersync validate`). The CLI does not provision or deploy to a remote server; for development, you can use **Docker** to run a local PowerSync Service (and optional DB/storage) on your machine.
Copy link
Collaborator

@kobiebotha kobiebotha Feb 26, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm wondering if we should mention here that the CLI can also be used to quickly bootstrap a new self-hosted project i.e. powersync docker configure

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants