History

alex 25656cef67 Allow null origins on dotcom worker requests (#4105 ) GET requests to the same origin don't send the `origin` headers. in other situations we care about (CORS requests) we want to block unknown origins, but if the origin header is missing it's probably because this is a same-origin request, so we should allow it. Fixes an issue loading bookmarks on mobile devices ### Change type - [x] `bugfix`		2024-07-09 10:08:28 +00:00
..
src	Allow null origins on dotcom worker requests (#4105 )	2024-07-09 10:08:28 +00:00
.gitignore	unbrivate, dot com in (#2475 )	2024-01-16 14:38:05 +00:00
CHANGELOG.md	unbrivate, dot com in (#2475 )	2024-01-16 14:38:05 +00:00
package.json	put sync stuff in bemo worker (#4060 )	2024-07-03 14:10:54 +00:00
README.md	unbrivate, dot com in (#2475 )	2024-01-16 14:38:05 +00:00
tsconfig.json	put sync stuff in bemo worker (#4060 )	2024-07-03 14:10:54 +00:00
wrangler.toml	add workers-shared package and source-maps for dotcom-worker sentry reports (#4052 )	2024-07-02 09:10:20 +00:00

README.md

@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>