Skip to content

Commit ad4b319

Browse files
committed
clarify diagnostics app setup
1 parent 4760f81 commit ad4b319

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

tools/diagnostics-app/README.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,8 +24,12 @@ Then in this directory run:
2424
pnpm dev
2525
```
2626

27+
The app is now available on [http://localhost:5173/](http://localhost:5173/).
28+
2729
Generate a [development token](https://docs.powersync.com/usage/installation/authentication-setup/development-tokens) and sign in. For development tokens, the PowerSync endpoint should be populated automatically. For some others like Supabase tokens, it needs to be entered manually.
2830

31+
If you run powersync inside docker (such as via the [self-host-demo](https://github.com/powersync-ja/self-host-demo)) the returned powersync_url is internal to the docker network and will be unreachable outside of it. Since we run the diagnostics app outside of docker, you can then connect to the endpoint as exposed by docker-proxy, e.g. `http://localhost:8080`.
32+
2933
**Note**: Please see the known usability issues listed below.
3034

3135
## Functionality

0 commit comments

Comments
 (0)