NarrativeScience-old
Changing /socket.io/ route behind reverse proxy
Due to the geographic location of my server, i'm unable to open any ports other then 80,443 to bypass this problem. I currently have a socket.io application running on this server, and would like to use log.io to view the existing application log files. I am able access log.io's http server using NGINX reverse proxy. (using this method: https://github.com/NarrativeScience/Log.io/issues/142 )
But the socket.io route is conflicting with the existing socket.io application. Whats the best way to change the socket.io resource: / path: on both the server and client of log.io? I've done some experimentation and managed to change the client browser JS path from log.io.js, but im not sure if this is the best method? Any information would be appreciated.
would be great if the log_server.conf conf file has something like:
url_prefix: 'logio'
so that the url can be accessed as http://127.0.0.1:28777/logio
which would make life much more easier for proxying.
