Comments (2)
@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.
Related Issues (20)
- Update chokidar HOT 4
- client can't be found HOT 3
- Failling to load livereload dependency HOT 1
- Docker + browser extension, "Cannot download livereload.js" HOT 11
- Should reload when the exact path is changed HOT 3
- livereload.js request is hanging attempting to GET through a reverse proxy connection. no debug output available. HOT 1
- Feature request: Enable error message or logging levels to trace errors to stdout if things dont work. HOT 2
- Support proxied socket URL connections when running livereload from the command line. i.e. allow definition of a public socket URL. HOT 2
- javascript code auto injected in HTML page HOT 3
- livereload --debug disables file watcher HOT 11
- Feature request: support refreshing when an endpoint returns 200 HOT 1
- Command line for multiple path seems to be broken in 0.9.2 HOT 2
- Exclusions not working? HOT 7
- Improve documentation in README for how exclusions work
- feature request: support CORS for hosts HOT 1
- Require is not defined.
- Support configuring the interface (i.e. host) the server will listen to HOT 1
- Cannot use multiple node-livereload servers on one page HOT 1
- ENOSPC: System limit for number of file watchers reached
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from node-livereload.