Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify a custom server doesn't mean you can't use an existing backend. #23200

Merged
merged 3 commits into from
Mar 18, 2021
Merged

Clarify a custom server doesn't mean you can't use an existing backend. #23200

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
140cc2f
Clarify a custom server doesn't mean you can't use an existing backend.
leerob Mar 18, 2021
202e196
Update docs/advanced-features/custom-server.md
leerob Mar 18, 2021
2c5f729
Update docs/advanced-features/custom-server.md
leerob Mar 18, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/advanced-features/custom-server.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ description: Start a Next.js app programmatically using a custom server.
</ul>
</details>

Typically you start your next server with `next start`. It's possible, however, to start a server 100% programmatically in order to use custom route patterns.
By default, Next.js includes it's own server with `next start`. If you have an existing backend, you can still use it with Next.js (this is not a custom server). A custom Next.js server allows you to start a server 100% programmatically in order to use custom server patterns.
leerob marked this conversation as resolved.
Show resolved Hide resolved

> A custom server **can not** be deployed on [Vercel](https://vercel.com/solutions/nextjs), the platform Next.js was made for.

Expand Down