You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/supabase.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,15 +37,15 @@ When you need the daemon + browser to share a Supabase-issued token (useful for
37
37
pnpm --filter @powersync-community/powergit login
38
38
```
39
39
40
-
The CLI prints a device code and a verification URL (`POWERSYNC_DAEMON_DEVICE_URL`, default `http://localhost:5783/auth`). Open it, sign in, and the token is stored under `~/.powergit`.
40
+
The CLI prints a device code and a verification URL (`POWERSYNC_DAEMON_DEVICE_URL`, default `http://localhost:5783/auth`). Open it, sign in, and the token is stored under `~/.powergit/daemon/<profile>/`.
41
41
42
42
### CLI live tests (optional)
43
43
44
44
When you have the local PowerSync + Supabase stack running (for example via `pnpm dev:stack` or your own Docker Compose deployment), you can run an additional Vitest suite that exercises `powergit sync` against the live services. Provide the connection details through environment variables so the test can discover the stack:
45
45
46
46
| Variable | Purpose |
47
47
| --- | --- |
48
-
|`POWERGIT_TEST_REMOTE_URL`|PowerSync remote URL (e.g. `powergit::https://localhost:8080/orgs/acme/repos/infra`). *Required to enable the test.*|
48
+
|`POWERGIT_TEST_REMOTE_URL`|Powergit remote URL (e.g. `powergit::/acme/infra`, `powergit::staging/acme/infra`, or `powergit::local-dev/acme/infra`). *Required to enable the test.*|
49
49
|`POWERGIT_TEST_REMOTE_NAME`| Git remote name to target (defaults to `powersync`). |
50
50
|`POWERGIT_TEST_SUPABASE_URL`| Supabase REST URL (used for password login). |
51
51
|`POWERGIT_TEST_SUPABASE_EMAIL`| Supabase user email used for HS256 login. |
Copy file name to clipboardExpand all lines: packages/cli/README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -71,9 +71,9 @@ git remote -v
71
71
> **Why `powergit::`?**
72
72
> Git uses the prefix before `::` to pick a remote helper binary named `git-remote-<prefix>`. We ship `git-remote-powergit`, so the URL must start with `powergit::`.
73
73
74
-
### Shorthand remote URLs (profiles/aliases)
74
+
### Shorthand remote URLs (profiles)
75
75
76
-
`powergit::/<org>/<repo>` uses the default profile (production out of the box). To target another stack, create a profile alias that bundles **both** the PowerSync and Supabase endpoints, then reference that alias in the remote URL:
76
+
`powergit::/<org>/<repo>` uses the default profile (production out of the box). To target another stack, create a profile that bundles **both** the PowerSync and Supabase endpoints, then reference that profile in the remote URL:
77
77
78
78
```bash
79
79
powergit profile set staging \
@@ -87,7 +87,7 @@ powergit profile set staging --set supabase.serviceRoleKey=<service-role-key>
Supabase credentials are **not** part of the remote URL. They live in the profile/env and are used only for login/auth, so prefer aliases when you need a non-prod or custom stack.
90
+
Supabase config (URL/anon key) and your login session are **not** part of the remote URL. Keep them in the profile/env (and never put a `supabase.serviceRoleKey` in a Git remote).
91
91
92
92
### Choose a different remote name
93
93
@@ -105,7 +105,7 @@ Before running commands that talk to PowerSync (push/fetch or `powergit sync`),
105
105
powergit login
106
106
```
107
107
108
-
`powergit login` uses Supabase credentials from your profile or environment (`SUPABASE_URL`, `SUPABASE_ANON_KEY`, `SUPABASE_EMAIL`, `SUPABASE_PASSWORD`). The resulting Supabase JWT is cached under `~/.powergit/session.json` and automatically reused by the CLI.
108
+
`powergit login` uses Supabase credentials from your profile or environment (`SUPABASE_URL`, `SUPABASE_ANON_KEY`, `SUPABASE_EMAIL`, `SUPABASE_PASSWORD`). The resulting Supabase JWT is cached per profile under `~/.powergit/daemon/<profile>/session.json` and automatically reused by the daemon.
109
109
110
110
Need to stash a token manually (for CI or when you already have one)?
0 commit comments