Isogenic Game Engine on c9.io problem

[Harry]

Hello. Can you explain me how to run multiplayer example project of isogenic game engine on c9.io?
I have installed this engine and then I do this:

node ./server/ige -g ./examples/24.1-network-stream

and then it happens

IGE *log* [IgeNetIoComponent] : Network component initiated with Net.IO version: 1.0.0
IGE *log* [IgeNetIoComponent] : Starting net.io listener on port 8080
IGE *log* [IgeNetIoComponent] : Starting client/server clock sync...
IGE *log* [NetIo.Server] : Server is listening on port 8080
IGE *log* [IgeEngine:ige] : Starting engine...
IGE *log* [IgeEngine:ige] : Engine started
IGE *log* [IgeStreamComponent] : Setting delta stream interval to 30ms
IGE *log* [IgeStreamComponent] : Starting delta stream...
IGE *log* [IgeNetIoComponent] : Server now accepting connections!

then I'm going to example project folder and run index.html file (or server.js) and it show this:

Started apache2
(98)Address already in use: AH00072: make_sock: could not bind to address [::]:8080
(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:8080
no listening sockets available, shutting down
AH00015: Unable to open logs

So what I'm doing wrong?

(sorry for mistakes. english is not my native language)

[mattstyles]

I know nothing of c9 or isogenic but looks like you're just trying to bind 2 things to 1 port, which isn't going to work.

Your first instruction starts a server listening on 8080 (I'm guessing you already worked that one out!), if you want something else to serve your front-end then it can't be trying to bind to 8080, hence the EADDRINUSE error.

Just tell apache or the server to bind to another port and you'll get both serving. 

You might additionally have to tell the front-end which host:port to try connecting to, thats app specific though, no way to tell from here whats going on with that piece.

It's possible that your first instruction serves the front-end as well, I'm assuming that the demo server exposes itself to localhost so have you tried just firing up the browser to port 8080 after running the ige process?