Relative path for serving assets and code about socketstream HOT 6 CLOSED

The HTTP side is intended to be essentially static in production. You generate bundles for HTML,CSS and JS. On demand JS is currently only supported on the server, but will be static as well in 0.6 or 0.8

So in production the only thing to proxy is the websocket connection and fallback support from SockJS/Engine.io

What I'm essentially saying is that there is nothing in SocketStream itself that needs to be handled in production. You just need to serve the static and assets directories from your HAProxy/Nginx frontend and proxy to the SocketStream server for the connection.

There is no particular support for configuring the path for where the fallback XHRs go. You'd have to refer to the transport documentation for that.

from socketstream.

Hmm, did you just mean the /assets/ URL? I haven't used the feature but when setting packAssets you can set an asset URL rewriting function. Look in docs for cdn

from socketstream.

@gbraad Is the issue solved for you?

from socketstream.

btw why would proxy rewrite be an issue, it's pretty standard

from socketstream.

I haven't been able to look into this further in recent time. The proxy rewrite would not be a problem, but having the flexibility from within socketstream to define the paths would be appreciated, although not essential. It would be considered advanced functionality. Note: the proxy-ing in question is really lightweight and does not involve nginx as it is done on a simple ARM-based device using only Node.js

from socketstream.

As mentioned above you can already do that with the CDN configuration for assets. It isn't clear to me what you are trying to achieve though as all HTTP traffic in production should be static assets or SockJS/Engineio traffic.

If there is no clear requirement or issue I will have to close this

from socketstream.