Configure API to work on Vercel from Next SSR #41
Conversation
- Set up axios instance to use correct public Vercel URL for API calls
during server-side rendering
- Inject user's client-side cookies during API request
- Create demo example to illustrate server-side API call with axios and
a native POST request from the client
- Update Uvicorn `host` to resolve IPv6 issues
- Configure Next rewrite which acts like a Vercel rewrite
- This allows for local client-side testing of API endpoints and makes
the API paths publicly accessible at `/api/`
|
Deploy preview for irvinehacks-site-2024 ready!
|
|
Deploy preview for irvinehacks-site-2024-sanity ready!
|
There was a problem hiding this comment.
@waalbert was dealing with an Axios error related to IPv6 though (ECONNREFUSED ::1:8000) until he removed the ::1 entry from /etc/hosts. I'm pretty sure this isn't the proper way to resolve the error, but you did already change the Uvicorn host to localhost so I'm not too sure what the issue is here. To make matters even more peculiar, I'm not able to replicate the same error on my machine, perhaps due to an operating system/networking difference.
|
Interesting, on my machine, Node v16 resolves localhost to IPv4 whereas Node v17, v18, and v19 resolve IPv6 first, but interestingly Node v20 resolves IPv4 first. None of the versions seem to respect the order of the hosts file. |
|
Ok that makes more sense. Currently, I'm on Node 20. |
Changes
hostto resolve IPv6 issues/api/Testing
Clone the branch locally and visit
/demowhile also having the local API server running with UvicornusernameVisit
/demoin the deployed preview