Tom Ballinger
Tom Ballinger
> Shouldn't the environment variables defined by convex with pnpx convex env set be located in a very specific convex folder, as you said .convex/? This is pretty different, `convex...
> In my opinion, interaction with the CLI should be optional. Absolutely, this is important. The only guaranteed way to make `convex dev` non-interactive today is to 1) use a...
> However, I am unable to specify an environment file or use the one provided through process.env, as I use dotenv-run to spread that root .env file across my packages...
Would love to hear more, so far I'm hearing 1. Let's provide a way to specify a different file than .env.local (e.g. ../../.env) to write CONVEX_URL to 2. (lower priority)...
I broke 1) out into https://github.com/get-convex/convex-backend/issues/206
Hi @widavies, thanks for writing this out. This is a limitation of `expectAuth: true`, and a reason we're not yet recommending this path and it's still an experimental option: if...
Here's a proof of concept here that I haven't tested https://github.com/get-convex/convex-js/pull/83 Writing this out helped me think through that this should work for you if you used ``, and what...
What happens when you run `npx convex dev` in that directory?
The behavior I think I want is "`npx convex dev --local` works, and changes the default locally to local until you run `npx convex dev --cloud` which changes the default...
This is a nice change but we're thinking we want to go the other direction here: we've found it gets complicated to write client-side middleware when it's all conditional on...