Make Supabase CLI read .env from a different location when using --workdir

[BertVanHecke]

I’d like to move my Supabase project folder to a different location instead of keeping it in the root. I know about using the --workdir flag with the Supabase CLI to point to the folder with config.toml. However, since moving it, my .env file (which lives in the project root) is no longer being read, and I’m getting warnings that variables like SUPABASE_AUTH_GITHUB_CLIENT_ID are unset.

Does anyone know what the correct way is to configure the Supabase CLI so that it picks up environment variables from a .env file in a different location?

[BertVanHecke]

Turns out that I have to install dotenv and run the command like this: dotenv -e ./.env -- supabase start --workdir ./src/lib.

It works, but it would be nice if I could just configure this in the config.toml file.