How am I supposed to use Wranglers open source with env variables?
Original message was deleted
GYou can use custom generated wrangler config files
https://developers.cloudflare.com/workers/wrangler/configuration/#generated-wrangler-configuration
but that still requires people that use your project write their db name and id to an env file or a github secret store or whatever it may be.
Or just make it easy and in your open source project put placeholder values for d1 in your wrangler config, eg "<your d1 db id here">, update your readme, and move on to building your features.
I hope that helps, good luck!
https://developers.cloudflare.com/workers/wrangler/configuration/#generated-wrangler-configuration
but that still requires people that use your project write their db name and id to an env file or a github secret store or whatever it may be.
Or just make it easy and in your open source project put placeholder values for d1 in your wrangler config, eg "<your d1 db id here">, update your readme, and move on to building your features.
I hope that helps, good luck!
Cloudflare Docs
Use a configuration file to customize the development and deployment setup for your Worker project and other Developer Platform products.
Gthis is probably interesting to you @oSumAtrIX https://discord.com/channels/595317990191398933/1040420029080018945/1399781350894080053
GThere are a lot of good reasons not to use .env, largely related to the fact that these are edge runners without OS access + security concerns. I think if this is a hill worth dying on for you, you should consider another platform OR again, just source control a wrangler config with placeholders. I wish you the best of luck 
Tits ok to check in .env files that contain non-sensitive data. It is a strategy used by many frameworks.
TThere is also some new features coming to wrangler soon that will allow you to use
.env.dev.varsTnow regardless, binding env vars into your wrangler config (if you need that) gets a bit tricky unfortunately
TGitHub
Following on from #1929 —it's probably worthwhile having a discussion about the future of configuration for Wrangler, pulling together the various discussions there have been at different point...
Tfor now, you could add a little extra tooling that generates/updates a wrangler config as part of deployment
