1
0
Fork 0
mirror of https://github.com/terribleplan/next.js.git synced 2024-01-19 02:48:18 +00:00
next.js/examples/custom-server
Dan Zajdband c5d69f0585 Add/move examples (#470)
* Added redux and styled components (wip) examples.

* Updated examples readmes and package.json

* Fixed styled-components example
2016-12-21 21:10:54 -08:00
..
pages Programmatic API (#310) 2016-12-16 12:33:08 -08:00
package.json Programmatic API (#310) 2016-12-16 12:33:08 -08:00
README.md Add/move examples (#470) 2016-12-21 21:10:54 -08:00
server.js Programmatic API (#310) 2016-12-16 12:33:08 -08:00

Custom server example

How to use

Download the example:

curl https://codeload.github.com/zeit/next.js/tar.gz/master | tar -xz next.js-master/examples/custom-server
cd next.js-master/examples/custom-server

or clone the repo:

git clone git@github.com:zeit/next.js.git --depth=1
cd next.js/examples/custom-server

Install the dependencies:

npm install

Run the dev server:

npm start

The idea behind the example

Most of the times the default Next server will be enough but sometimes you want to run your own server to customize routes or other kind of the app behavior. Next provides a Custom server and routing so you can customize as much as you want.

The example shows a server that serves the component living in pages/a.js when the route /b is requested and pages/b.js when the route /a is accessed. This is obviously a non-standard routing strategy. You can see how this custom routing is being made inside server.js.