Move Away from Using Environment Variables for Secrets

Chore


Describe the chore


Currently, self-hosting supabase using docker is recommending environment variables for sensitive data ( This is generally discouraged, since exposing secrets as environment variables might be a security problem. Also a while back supabase began to make iterative changes to support *_FILE based environment to store paths to secrets. We should utilize this and start moving away from directly using environment variables for secrets.

(And of course, update the docs about this)

Additional context


For more context, this is what I mean. Currently, we store PGRST_JWT_SECRET=some_secret in .env file, and we load using

A better way to go about this is:


Additional resources:
Docker' .env:
Docker secrets:
Supabase self-hosted: