You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@ifjorissen ,
If you have simply cloned this repo or clicked the "Deploy to Vercel" button, I believe the next.config.js is currently configured to only deploy the Swagger UI if process.env.NODE_ENV === "development" which is not the case in a production Vercel deployment.
Check the live demo-- https://nextjs-fastapi-starter.vercel.app/
According to next.config.js, the swagger UI should be at https://nextjs-fastapi-starter.vercel.app/docs, and the openapi.json at https://nextjs-fastapi-starter.vercel.app/openapi.json
However, both of those 404.
Have cloned this project locally & deployed it to vercel and can confirm I see the same behavior.
Any ideas on how to get the swagger ui and openapi.json to route correctly? Thanks!
The text was updated successfully, but these errors were encountered: