Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow the API_EXTERNAL_URL used by the gotrue service to be set #2527

Closed
toBeOfUse opened this issue Jul 16, 2024 · 0 comments · Fixed by #2634
Closed

Allow the API_EXTERNAL_URL used by the gotrue service to be set #2527

toBeOfUse opened this issue Jul 16, 2024 · 0 comments · Fixed by #2634
Labels
enhancement New feature or request
Milestone

Comments

@toBeOfUse
Copy link

Is your feature request related to a problem? Please describe.
All of the email verification links generated when using a Supabase instance created by the CLI start with http://127.0.0.1. I believe that this is because this CLI always sets the API_EXTERNAL_URL environment variable to http://127.0.0.1 when creating the supabase/gotrue container. This is a problem when creating a Supabase instance using the CLI, and then trying to use it from outside of the current host, where 127.0.0.1 no longer refers to the machine that the gotrue container is running on.

Describe the solution you'd like
Ideally, the hostname in the links that the gotrue service creates would not always be 127.0.0.1. I believe that if a configuration option to set the API_EXTERNAL_URL option existed, it would allow us to change the generated URLs to use a different address or domain.

Describe alternatives you've considered
If there is any alternative way to set the hostnames that are used in email verification URLs, that would also be great.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants