Setting up worker for multiple enviroments
I have spent days on this it is just not easy or clear from the docs. I run into many issues where, for example if you have a top level bindings for things, like D1 but have other [env] it failes to build. But then when I try and create env's for say having a local dev I need to have D1 binding ID. Can ya'll not fix it to be a bit easier to do this? I have given up on even having a local D1 DB created and just decided to now have a central remote "dev" D1 DB but now when I configure that I get this error:
⛅️ wrangler 4.33.2 (update available 4.36.0)
─────────────────────────────────────────────
Support for remote bindings in
How does anyone setup a proper local dev enviroment with Wrangler?
wrangler dev is now available in public beta as a replacement for wrangler dev --remote. Try it out now by running wrangler dev --x-remote-bindings with the experimental_remote option enabled on your resources and let us know how it goes!
This gives you access to remote resources in development while retaining all the usual benefits of local dev: fast iteration speed, breakpoint debugging, and more.
✘ [ERROR] In development, you should use a separate r2 bucket than the one you'd use in production. Please create a new r2 bucket with "wrangler r2 bucket create <name>" and add its name as preview_bucket_name to the r2_buckets "attachments" in your wrangler.toml file
So now I have to create a R2 and D1 bucket with a certain prefix?? This is just such a mess.
And this makes no sense:
💡 Create a new D1 database with "wrangler d1 create <name>" and add its id as preview_database_id to the d1_database "DB" in your wrangler.toml file
So it's the same command but I need to call it preview_database_id?How does anyone setup a proper local dev enviroment with Wrangler?
1 Reply
And I just tried the new experimental x-remote flags but those can not be used with [env]. So frustrating.