There is an issue with starting everything from the root with bun dev run, the issue is, the ping app and api app seems to try to use the same wrangler debugging port: 9229
To fix the issue just assign two different ports within wrangler:
wrangler.jsonc apps/api
"dev": { "inspector_port": 9230 }
wrangler.jsonc apps/ping
"dev": { "inspector_port": 9232 }
At least this was the issue for me on a fresh repo clone.
Also suggestion for the readme: Currently this section:
bun db:up starts PostgreSQL and Tinybird Local in Docker. Before the first start, set BETTER_AUTH_SECRET, CREDENTIAL_MASTER_KEY_V1 and SQIDS_ALPHABET in the API's .dev.vars; the example file explains how to generate each value. Run the Tinybird push once for every fresh container to load its event tables and endpoints.
comes after the bun install etc. section which is easy to overlook at first, when you just try to run the project at first. Maybe add this section before showing commands like bun dev?
There is an issue with starting everything from the root with bun dev run, the issue is, the ping app and api app seems to try to use the same wrangler debugging port:
9229To fix the issue just assign two different ports within wrangler:
At least this was the issue for me on a fresh repo clone.
Also suggestion for the readme: Currently this section:
bun db:up starts PostgreSQL and Tinybird Local in Docker. Before the first start, set BETTER_AUTH_SECRET, CREDENTIAL_MASTER_KEY_V1 and SQIDS_ALPHABET in the API's .dev.vars; the example file explains how to generate each value. Run the Tinybird push once for every fresh container to load its event tables and endpoints.comes after the bun install etc. section which is easy to overlook at first, when you just try to run the project at first. Maybe add this section before showing commands like bun dev?