From 7a3e6053fa62bc325a8352cb607b337ab6e453d0 Mon Sep 17 00:00:00 2001 From: bean1352 Date: Thu, 8 Oct 2026 18:11:47 +0200 Subject: [PATCH 1/4] Polish cli status paragraph --- tools/cli.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/cli.mdx b/tools/cli.mdx index f73cc0a8b..747956a61 100644 --- a/tools/cli.mdx +++ b/tools/cli.mdx @@ -272,7 +272,7 @@ Then use the same commands as any self-hosted instance (`powersync status`, `pow | `powersync stop --confirm=yes` | [Cloud] Stop instance (restart with deploy) | | `powersync compact` | [Cloud] Trigger [bucket compacting](/maintenance-ops/compacting-buckets) on demand | -The CLI prints the instance it is about to act on before `powersync deploy`, `powersync stop`, `powersync destroy`, and `powersync compact` make any change, and at the start of `powersync status`. For a Cloud instance, the line shows the instance name with the instance, project, and organization IDs. For a self-hosted instance, it shows the API URL. Check this line before you confirm a destructive command. +`powersync deploy`, `powersync stop`, `powersync destroy`, `powersync compact`, and `powersync status` print the instance they act on as their first line of output. For a Cloud instance, the line shows the instance name with the instance, project, and organization IDs. For a self-hosted instance, it shows the API URL. To verify your target instance, run `powersync status`. Run `powersync --help` or `powersync --help` for flags. Full [command reference](https://github.com/powersync-ja/powersync-cli/blob/main/cli/README.md#commands) in the CLI repo. From d553a2bb4c38fe83c266d020f744607f3933931c Mon Sep 17 00:00:00 2001 From: bean1352 Date: Thu, 8 Oct 2026 18:15:16 +0200 Subject: [PATCH 2/4] Wording tweak --- tools/cli.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/cli.mdx b/tools/cli.mdx index 747956a61..f6894f2e5 100644 --- a/tools/cli.mdx +++ b/tools/cli.mdx @@ -272,7 +272,7 @@ Then use the same commands as any self-hosted instance (`powersync status`, `pow | `powersync stop --confirm=yes` | [Cloud] Stop instance (restart with deploy) | | `powersync compact` | [Cloud] Trigger [bucket compacting](/maintenance-ops/compacting-buckets) on demand | -`powersync deploy`, `powersync stop`, `powersync destroy`, `powersync compact`, and `powersync status` print the instance they act on as their first line of output. For a Cloud instance, the line shows the instance name with the instance, project, and organization IDs. For a self-hosted instance, it shows the API URL. To verify your target instance, run `powersync status`. +`powersync deploy`, `powersync stop`, `powersync destroy`, `powersync compact`, and `powersync status` print the target instance as their first line of output. For a Cloud instance, the line shows the instance name with the instance, project, and organization IDs. For a self-hosted instance, it shows the API URL. To verify your target instance, run `powersync status`. Run `powersync --help` or `powersync --help` for flags. Full [command reference](https://github.com/powersync-ja/powersync-cli/blob/main/cli/README.md#commands) in the CLI repo. From c3277582bfa6b5a2311835b6f793e7a7d83169d9 Mon Sep 17 00:00:00 2001 From: bean1352 Date: Thu, 8 Oct 2026 18:26:01 +0200 Subject: [PATCH 3/4] remove target instance paragraph from command reference --- tools/cli.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/tools/cli.mdx b/tools/cli.mdx index f6894f2e5..8b1fd1b1b 100644 --- a/tools/cli.mdx +++ b/tools/cli.mdx @@ -272,8 +272,6 @@ Then use the same commands as any self-hosted instance (`powersync status`, `pow | `powersync stop --confirm=yes` | [Cloud] Stop instance (restart with deploy) | | `powersync compact` | [Cloud] Trigger [bucket compacting](/maintenance-ops/compacting-buckets) on demand | -`powersync deploy`, `powersync stop`, `powersync destroy`, `powersync compact`, and `powersync status` print the target instance as their first line of output. For a Cloud instance, the line shows the instance name with the instance, project, and organization IDs. For a self-hosted instance, it shows the API URL. To verify your target instance, run `powersync status`. - Run `powersync --help` or `powersync --help` for flags. Full [command reference](https://github.com/powersync-ja/powersync-cli/blob/main/cli/README.md#commands) in the CLI repo. ## Deploying From CI (e.g. GitHub Actions) From 4d53d0983f76dc290183238b8a2c7593017e5e2d Mon Sep 17 00:00:00 2001 From: bean1352 Date: Thu, 8 Oct 2026 18:53:49 +0200 Subject: [PATCH 4/4] reword ci sentence that referenced the removed paragraph --- tools/cli.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/cli.mdx b/tools/cli.mdx index 8b1fd1b1b..280a0bd8d 100644 --- a/tools/cli.mdx +++ b/tools/cli.mdx @@ -280,7 +280,7 @@ You can automate Sync Config (and full config) deployments using the CLI in CI. **Secrets:** Set `PS_ADMIN_TOKEN` to your PowerSync personal access token. If the workflow does not use a linked directory, also set `INSTANCE_ID`. For self-hosted, `API_URL` can specify the PowerSync API base URL. -The job log records the target instance line, so you can see which instance a run changed. For pull request checks, run `powersync deploy --dry-run` to validate the config and preview the changes without deploying. +The job log shows which instance the run changed. For pull request checks, run `powersync deploy --dry-run` to validate the config and preview the changes without deploying. Example: deploy Sync Config on push to main