Update Next.js deployment notes#7771
Conversation
Hi @eduardoboucas! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
How did the Vercel mention even get into this page? I didn’t write that when I was writing it originally. |
cc @mattcarrollcode. i think the idea was to be transparent, and differentiate next and vercel, but i agree it's misplaced. |
It definitely reads like a promotion which def wasn't the intent lol |
I like the new version better. Thank you! |
This PR updates the notes about deployment options on the Next.js (App Router) section with the following changes:
Replaces the mention of "serverless hosting" with "Docker containers" to reflect the three self-hosting options listed on https://nextjs.org/docs/app/guides/self-hosting. It is currently not true that you can deploy Next.js to any serverless hosting provider, as confirmed by the Deployment Adapters API RFC. This issue is described in more detail here.
Removes the reference to Vercel paid cloud services. There are other cloud providers also offering different paid services that apply to Next.js sites, so I don't think there's a reason to single out Vercel's in this case.