-
Notifications
You must be signed in to change notification settings - Fork 793
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
Add deployment section in docs #1140
Labels
enhancement
New feature or request
Comments
Thanks, we see some users struggling with the CORS issue when not updating the App URL for hosted environments. Any ideas how we can improve the docs are welcome. Though we generally recommend to create two projects on Hanko Cloud, one for development, and one for hosted / production deployment. This has the following benefits:
We probably should think about how we can make this more clear on Hanko Cloud as well. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checklist
Description
I recently encountered an issue during the deployment of a Next.js project on Vercel, where CORS (Cross-Origin Resource Sharing) issues emerged after deployment. I believe this issue could be addressed in the documentation to help new developers avoid this common pitfall and improve their deployment experience.
Describe your ideal solution
To avoid CORS issues, it's necessary to update the application's URL or domain configuration after deployment. This can typically be done in the Hanko Cloud Console under settings -> general -> appurl
By making this simple adjustment, it'll avoid unnecessary troubleshooting.
Workarounds or alternatives
No response
Hanko Version
0.8.4
Additional Context
No response
The text was updated successfully, but these errors were encountered: