Bug/add namespace to websocket

[Alescontrela]

Modifies CryptoBook-js to conform to CryptoBook's api call syntax. Connections to the websocket are now established via a route:

sio.connect('http://0.0.0.0:5050/api/v1/real_time')

which allows us to generalize the port (in this case 5050) using nginx.

[synchronizing]

Modifies CryptoBook-js to conform to CryptoBook's api call syntax. Connections to the websocket are now established via a route:

sio.connect('http://0.0.0.0:5050/api/v1/real_time')

which allows us to generalize the port (in this case 5050) using nginx.

Big issue, the Cryptobook API-endpoint is /api/v1/cryptobook/<endpoint>, that's what we have been conforming too. However, I am down to have a conversation on perhaps modifying it to /api/v1/ and instead route to cryptobook with nginx on the larger structure. Also, what do you think of /api/v1/cryptobook/live or /api/v1/live?

[Alescontrela]

I'm fine with either of those. It's a pretty simple change. I'll make the switch to /api/v1/cryptobook/live.

[synchronizing]

I'm fine with either of those. It's a pretty simple change. I'll make the switch to /api/v1/cryptobook/live.

Sounds good. Feel free to merge if small change, or if need for review, lmk.