Due to a complex backend inherited situation, I have an nginx setup through which I am trying to proxy to elm-live when I develop. Here is the nginx config:
When I to to 127.0.0.1:3000 and make changes, hot reloading works. I can see that modified HTML pointing to the reload.js file in my sources. Note however that this is not a workaround, as this app cannot proxy to the backend so it doesn't do much.
When I go to my nginx endpoint (hostname.me:8080), I can see the app working, but hot-reloading doesn't work. When I go to the sources folder, I can see that the HTML file is modified to include reload.js, but the file doessn't itself seem to be served.
Due to a complex backend inherited situation, I have an nginx setup through which I am trying to proxy to elm-live when I develop. Here is the nginx config:
I run elm-live like this
When I to to 127.0.0.1:3000 and make changes, hot reloading works. I can see that modified HTML pointing to the reload.js file in my sources. Note however that this is not a workaround, as this app cannot proxy to the backend so it doesn't do much.
When I go to my nginx endpoint (hostname.me:8080), I can see the app working, but hot-reloading doesn't work. When I go to the sources folder, I can see that the HTML file is modified to include reload.js, but the file doessn't itself seem to be served.
Why is that? Is there a way to fix it?