CLI configuration

A string used to distinguish different Supabase projects on the same host. Defaults to the working directory name when running supabase init.

The base URL of your website. Used as an allow-list for redirects and for constructing URLs used in emails.

A list of exact URLs that auth providers are permitted to redirect to post authentication.

How long tokens are valid for, in seconds. Defaults to 3600 (1 hour), maximum 604,800 seconds (one week).

Allow/disallow new user signups to your project.

Allow/disallow new user signups via email to your project.

If enabled, a user will be required to confirm any email change on both the old, and new email addresses. If disabled, only the new email is required to confirm.

If enabled, users need to confirm their email address before signing in.

Use an external OAuth provider. The full list of providers are:

• apple
• azure
• bitbucket
• discord
• facebook
• github
• gitlab
• google
• twitch
• twitter
• slack
• spotify

Client ID for the external OAuth provider.

Client secret for the external OAuth provider.

The base URL used for constructing the URLs to request authorization and access tokens. Used by gitlab and keycloak. For gitlab it defaults to https://gitlab.com. For keycloak you need to set this to your instance, for example: https://keycloak.example.com/realms/myrealm .

The URI a OAuth2 provider will redirect to with the code and state values.

Port to use for the API URL.

Schemas to expose in your API. Tables, views and functions in this schema will get API endpoints. public and storage are always included.

Extra schemas to add to the search_path of every request. public is always included.

The maximum number of rows returned from a view, table, or stored procedure. Limits payload size for accidental or malicious requests.

Port to use for the local database URL.

Port to use for the local shadow database.

The database major version to use. This has to be the same as your remote database's. Run SHOW server_version; on the remote database to check.

Port to use for Supabase Studio.

Port to use for the email testing server web interface.

Emails sent with the local dev setup are not actually sent - rather, they are monitored, and you can view the emails that would have been sent from the web interface.

Port to use for the email testing server SMTP port.

Emails sent with the local dev setup are not actually sent - rather, they are monitored, and you can view the emails that would have been sent from the web interface.

If set, you can access the SMTP server from this port.

Port to use for the email testing server POP3 port.

Emails sent with the local dev setup are not actually sent - rather, they are monitored, and you can view the emails that would have been sent from the web interface.

If set, you can access the POP3 server from this port.

The maximum file size allowed (e.g. "5MB", "500KB").

By default, when you deploy your Edge Functions or serve them locally, it will reject requests without a valid JWT in the Authorization header. Setting this configuration changes the default behavior.

Note that the --no-verify-jwt flag overrides this configuration.

Specify the Deno import map file to use for the Function.

Note that the --import-map flag overrides this configuration.