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
[](https://deploy.now.sh/?repo=https://github.com/zeit/next.js/tree/master/examples/custom-server-micro)
2
+
3
+
# Custom Micro Server example
4
+
5
+
## How to use
6
+
7
+
Download the example [or clone the repo](https://github.com/zeit/next.js):
8
+
9
+
```bash
10
+
curl https://codeload.github.com/zeit/next.js/tar.gz/master | tar -xz --strip=2 next.js-master/examples/custom-server-micro
11
+
cd custom-server-micro
12
+
```
13
+
14
+
Install it and run:
15
+
16
+
```bash
17
+
npm install
18
+
npm run dev
19
+
```
20
+
21
+
Deploy it to the cloud with [now](https://zeit.co/now) ([download](https://zeit.co/download))
22
+
23
+
```bash
24
+
now
25
+
```
26
+
27
+
## The idea behind the example
28
+
29
+
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.
30
+
31
+
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 micro and micro-route to build a custom router on top of Next.
32
+
33
+
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