←back to thread

Show HN: Self-Host Next.js in Production

(github.com)
90 points vednig | 1 comments | 20 Nov 24 22:07 UTC | HN request time: 0.214s | source
Show context
Etheryte ◴[20 Nov 24 23:05 UTC] No.42199068[source]▶
I haven't really followed Next.js and the related ecosystem closely, what does this project do exactly? If I look at Next.js docs [0], they have three options for self-hosting: using a Node server, using a Docker container or as an SPA. Is this project a wrapper around one of those or is it something else entirely? Or to perhaps ask differently, to me it seems you can already self-host Next.js, what's the value add of this specific project?

[0] https://nextjs.org/docs/pages/building-your-application/depl...

replies(6): >>42199156 #>>42199158 #>>42199207 #>>42199214 #>>42199340 #>>42200321 #
grrowl ◴[20 Nov 24 23:24 UTC] No.42199207[source]▶
You can "self-host" as in `next build` and `next serve`, but it runs as a monolothic runtime. Next-on-vercel compiles each api route to a serverless function and supports various additional flavours of server side rendering of pages. Open Next is being able to run like Next-on-vercel but on AWS, your own infra, Cloudflare Workers, and others.
replies(1): >>42200038 #
dvnguyen ◴[21 Nov 24 01:20 UTC] No.42200038[source]▶
Gotcha. That means if I run Next for just frontend + server side rendering stuff then I can always self host it?
replies(1): >>42200523 #
1. presentation ◴[21 Nov 24 02:36 UTC] No.42200523[source]▶
Sort of, so long as you don’t care about more complex hosting strategies eg hosting some/all of your server side code on edge servers when users visit your web app - as opposed to always sending them to a server in a set location in the world as a “normal” server architecture would typically do. Alongside not caring about prerendering and caching some pages and not others, that kind of thing