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

Defining the "Main Deployment URL" #296

Open
guylepage3 opened this issue Feb 14, 2024 · 2 comments
Open

Defining the "Main Deployment URL" #296

guylepage3 opened this issue Feb 14, 2024 · 2 comments

Comments

@guylepage3
Copy link
Contributor

guylepage3 commented Feb 14, 2024

I just ran through the deployment process on the README.md and it reads well.

One thing that needs much better defining however is...

In your Supabase project, navigate to auth > URL configuration and set your main production URL (e.g. https://your-deployment-url.vercel.app/) as the site url.

When the user visits their Vercel > Project > Production Deployment page, they will see 4+ URL's and none of them have a title of "Main Production URL". We should define which of the URL's is their "Main Production URL".

I actually do not know which one is their "Main Production URL" or I would do a pull request.

I am "guessing" that the "Main Production URL" being mentioned is actually the URL under "Domains" and set as

Domains
https:// [ vercel-project-name ] .vercel.app

NOT

Deployment
https:// [ vercel-project-name ] - [ hash ] - [ username ] .vercel.app

Domains
https:// [ vercel-project-name ] - [ username ] .vercel.app

Domains
https:// [ vercel-project-name ] - [ git-main ] - [ username ] .vercel.app
@guylepage3
Copy link
Contributor Author

If someone could let me know if that is correct I can create a pull request.

@thorwebdev
Copy link
Collaborator

Hey, yes, it's either https:// [ vercel-project-name ] .vercel.app or your custom domain if you have one.

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

No branches or pull requests

2 participants