You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Download the example [or clone the repo](https://github.com/zeit/next.js):
7
+
8
+
```bash
9
+
curl https://codeload.github.com/zeit/next.js/tar.gz/master | tar -xz --strip=2 next.js-master/examples/custom-server-koa
10
+
cd custom-server-koa
11
+
```
12
+
13
+
Install it and run:
14
+
15
+
```bash
16
+
npm install
17
+
npm run dev
18
+
```
19
+
20
+
Deploy it to the cloud with [now](https://zeit.co/now) ([download](https://zeit.co/download))
21
+
22
+
```bash
23
+
now
24
+
```
25
+
26
+
## The idea behind the example
27
+
28
+
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.
29
+
30
+
Because the Next.js server is just a node.js module you can combine it with any other part of the node.js ecosystem. in this case we are using [Koa](http://koajs.com/) to build a custom router on top of Next.
31
+
32
+
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`.
0 commit comments