-
Notifications
You must be signed in to change notification settings - Fork 711
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
Vercel deployment should be modified to not require Leap #118
Comments
where are you seeing this? can you share a link + screenshot? |
@Precious-Macaulay any idea why this might happen? |
it is already updated with what i can see here |
I think the deploy link on the README includes some old references to leap, but I'm not sure how to create a proper deployment link with the updated links and not including LEAP_API_KEY |
this is the link at vercel deployment : https://vercel.com/templates/next.js/headshot-ai
|
Can you just ignore those env vars for now? |
Yes, and also the link from the README is different from the vecel template link. Thank you so much, trying it now =) |
Especially if people are using this on Vercel just to try out the auth with Supabase, they shouldn't be required to enter the Leap webhook secret key (it's not even clear where one would get this).
The text was updated successfully, but these errors were encountered: