next.js/examples/custom-server/README.md


# Custom server example

## How to use

Download the example (or clone the repo)[https://github.com/zeit/next.js.git]:

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

Install it and run:

```bash
npm install
npm run dev
```

Deploy it to the cloud with [now](https://zeit.co/now) ([download](https://zeit.co/download))

```bash
now
```

## 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](https://github.com/zeit/next.js#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`.
Add/move examples (#470) * Added redux and styled components (wip) examples. * Updated examples readmes and package.json * Fixed styled-components example 2016-12-22 05:10:54 +00:00
			`# Custom server example`

			`## How to use`

Add/data fetch example (#485) * Added data fetch example * Finished updating examples install instructions and added data-fetch example to main readme 2016-12-22 23:05:49 +00:00			`Download the example (or clone the repo)[https://github.com/zeit/next.js.git]:`
Add/move examples (#470) * Added redux and styled components (wip) examples. * Updated examples readmes and package.json * Fixed styled-components example 2016-12-22 05:10:54 +00:00
			```bash
examples: simplify download instruction 2016-12-22 09:07:54 +00:00			`curl https://codeload.github.com/zeit/next.js/tar.gz/master \| tar -xz --strip=2 next.js-master/examples/custom-server`
			`cd custom-server`
Add/move examples (#470) * Added redux and styled components (wip) examples. * Updated examples readmes and package.json * Fixed styled-components example 2016-12-22 05:10:54 +00:00			```

Add/data fetch example (#485) * Added data fetch example * Finished updating examples install instructions and added data-fetch example to main readme 2016-12-22 23:05:49 +00:00			`Install it and run:`
Add/move examples (#470) * Added redux and styled components (wip) examples. * Updated examples readmes and package.json * Fixed styled-components example 2016-12-22 05:10:54 +00:00
			```bash
			`npm install`
fix npm script on examples 2016-12-26 03:59:09 +00:00			`npm run dev`
Add/move examples (#470) * Added redux and styled components (wip) examples. * Updated examples readmes and package.json * Fixed styled-components example 2016-12-22 05:10:54 +00:00			```

Add/data fetch example (#485) * Added data fetch example * Finished updating examples install instructions and added data-fetch example to main readme 2016-12-22 23:05:49 +00:00			`Deploy it to the cloud with [now](https://zeit.co/now) ([download](https://zeit.co/download))`
Add/move examples (#470) * Added redux and styled components (wip) examples. * Updated examples readmes and package.json * Fixed styled-components example 2016-12-22 05:10:54 +00:00
			```bash
Add/data fetch example (#485) * Added data fetch example * Finished updating examples install instructions and added data-fetch example to main readme 2016-12-22 23:05:49 +00:00			`now`
Add/move examples (#470) * Added redux and styled components (wip) examples. * Updated examples readmes and package.json * Fixed styled-components example 2016-12-22 05:10:54 +00:00			```

			`## 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](https://github.com/zeit/next.js#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`.