c9af23c921
This is for maintainabilty of the paths. It's hard to track down all the places where a route is being referenced. This helps unify them so that it's easily searchable in the codebase. This came up during the readonly room refactor and being able to find the way a particular route was wired through the codebase. ### Change Type <!-- ❗ Please select a 'Scope' label ❗️ --> - [x] `sdk` — Changes the tldraw SDK - [ ] `dotcom` — Changes the tldraw.com web app - [ ] `docs` — Changes to the documentation, examples, or templates. - [ ] `vs code` — Changes to the vscode plugin - [ ] `internal` — Does not affect user-facing stuff <!-- ❗ Please select a 'Type' label ❗️ --> - [ ] `bugfix` — Bug fix - [ ] `feature` — New feature - [ ] `improvement` — Improving existing features - [x] `chore` — Updating dependencies, other boring stuff - [ ] `galaxy brain` — Architectural changes - [ ] `tests` — Changes to any test code - [ ] `tools` — Changes to infrastructure, CI, internal scripts, debugging tools, etc. - [ ] `dunno` — I don't know |
||
---|---|---|
.. | ||
scripts | ||
src/lib | ||
.gitignore | ||
CHANGELOG.md | ||
package.json | ||
README.md | ||
tsconfig.json | ||
wrangler.toml |
@tldraw/tlsync-worker
Enable database persistence for local dev
The values for env.SUPABASE_KEY
and env.SUPABASE_URL
are stored in the Cloudflare Workers dashboard for this worker. However we use --local
mode for local development, which doesn't read these values from the dashboard.
To workaround this, create a file called .dev.vars
under merge-server
with the required values (which you can currently find at https://app.supabase.com/project/bfcjbbjqflgfzxhskwct/settings/api). This will be read by wrangler dev --local
and used to populate the environment variables.
SUPABASE_URL=<url>
SUPABASE_KEY=<key>