Possible to specify a different path prefix? about node-livereload HOT 2 OPEN

@krumware This actually wouldn't be terribly difficult to add, but I don't know if it's worth adding the options, docs, etc given the specificity of the use case. Can you give me an idea of how common this would be and more detail on why someone would want to do this? I think I understand but I'd like a clearer picture.

from node-livereload.

I'm doing this from memory, so apologies if this is off base:

I think the most common example may be if I deploy multiple front ends at different paths on the same port.

I may have app1 app2 and apple, which each have separate live reload instances. But they each are accessible via path prefix, so mysite/app1, mysite/app2, and mysite/app3.

When deploying to a live environment, I cant open any port I choose, so I can't use separate ports for each frontend in addition to each live reload server. I need to use paths to direct traffic in this instances.

What I can do, is have my load balancer direct certain paths to certain internal ports. Such as mysite:80/app1/livereload.js -> internalservice:3002/livereload.js, but I had trouble, I believe, with request header matching and the way it seems to function with the path match with the port and served at root. So the socket and script are not accessible. Does that make sense?

Thanks for the help!

from node-livereload.