mirror of https://github.com/terribleplan/next.js.git synced 2024-01-19 02:48:18 +00:00

History

Adrian le Bas c66cafd362 Remove hardcoded address from ws example. (#2204 ) With a hard coded address on the client, the app no longer works when deploying, which is annoying since there's a handy 'deploy now' button on the readme. By removing the hard coded address socket.io will connect to the location host automatically so it works both on development and production.		2017-06-08 19:11:08 +02:00
..
pages	Remove hardcoded address from ws example. (#2204 )	2017-06-08 19:11:08 +02:00
package.json	Add socket.io example (#1766 )	2017-04-22 14:53:48 +02:00
README.md	Add socket.io example (#1766 )	2017-04-22 14:53:48 +02:00
server.js	Add socket.io example (#1766 )	2017-04-22 14:53:48 +02:00

README.md

Socket.io example

How to use

Download the example or clone the repo:

curl https://codeload.github.com/zeit/next.js/tar.gz/master | tar -xz --strip=2 next.js-master/examples/with-socket.io
cd with-socket.io

Install it and run:

npm install
npm run dev

The idea behind the example

This example show how to use socket.io inside a Next.js application. It uses getInitialProps to fetch the old messages from a HTTP endpoint as if it was a Rest API. The example combine the WebSocket server with the Next server, in a production application you should split them as different services.

Example: https://next-socket-io.now.sh/