2
Make Supabase CLI read .env from a different location when using --workdir
Source: supabase/supabase#38152 · opened by @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?
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?
No pledges yet. Be the first to back this.
Comments
Similar requests
Local supabase studio and supabase dashboard looks too similar.
3 votes · 0 comments
Configure External PostgreSQL for Supabase Instead of supabase-db
3 votes · 0 comments
Add Reverse Proxy Support for Local Supabase Development
1 vote · 0 comments
Decouple supabase CLI from docker
1 vote · 0 comments
Git-based Schema Management w/ Supabase CLI
9 votes · 0 comments
No comments yet.