When running supabase locally as docker, It's impossible to to assign a value of environment variable to site_url in config.toml.

[GA1]

Bug report

• [] I confirm this is a bug with Supabase, not with my own application.
• [] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

When running supabase locally as docker, It's impossible to to assign a value of environment variable to site_url in config.toml.

To Reproduce

I used supabase-cli to create a supabase directory with the default config:

In the config I replaced the site_url with a custom hardcoded url: localhost:5173 because I wanted my google sign in work locally, and localhost:5173 is the address of my local frontend application.

Unfortunately when I try to replace the hardcoded url with an environment variable (that I provide during the run of supabase)

[auth]
enabled = true
# The base URL of your website. Used as an allow-list for redirects and for constructing URLs used
# in emails.
site_url = "env(SUPABASE_CONFIG_SITE_URL)"
# A list of *exact* URLs that auth providers are permitted to redirect to post authentication.
additional_redirect_urls = ["https://127.0.0.1:3000"]
# How long tokens are valid for, in seconds. Defaults to 3600 (1 hour), maximum 604,800 (1 week).
jwt_expiry = 3600
# If disabled, the refresh token will never expire.

the site_url is not getting replaced, instead it's understood as string, and used as such, what can be seen in one of the redirects I get in the browser:

http://localhost:54321/env(SUPABASE_CONFIG_SITE_URL)#access_token=....

Expected behavior

The site_url should be replaced with the value of SUPABASE_CONFIG_SITE_URL just like other parameters in the config are replaced with other variables

System information

• OS: macOS Sonoma 14.1.2
• Version of Node.js: [e.g. 20.11.1]
• Supabase-cli version: 1.150.0