3 ms·
Hey there, what issue are you having self-hosting Next.js? https://nextjs.org/docs/app/building-your-application/deploying#self-hosting https://nextjs.org/docs
by leerob 2y ago
Hey there, what issue are you having self-hosting Next.js?
https://nextjs.org/docs/app/building-your-application/deploying#self-hosting https://nextjs.org/docs/app/building-your-application/deploy...
- mmarian 2y agoMiddleware can only use a subset of NodeJS APIs https://github.com/vercel/next.js/discussions/46722 https://github.com/vercel/next.js/discussions/46722
- leerob 2y agoMiddleware is still fully supported when self-hosting. I agree that it would be helpful to have a Node.js route level middleware primitive. This primitive, for "global" middleware, intentionally has a limited runtime. https://nextjs.org/docs/app/building-your-application/deploying#middleware https://nextjs.org/docs/app/building-your-application/deploy...
- sharms 2y agoHey Lee - I tried setting up a self hosted POC today and it looks pretty tricky: * The shared cache loader is left to the user to implement (instead of say, just pass a Redis URL) * The revalidate XYZ doesn't seem to work with Cloudfront etc * The image lambda is left to the user * The Cache-Control header isn't correct