You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like the live reload of the marpit server always tries to connect to localhost. This doesn't work if you use a different hostname. Especially in the era of remote editing this is not uncommon. It would be nice if:
the current hostname used to access the server was used instead of the hardcoded localhost
ideally the same port was used for the websocket instead of a different port (just use a subpath like /live-reload-ws)
By doing so it would work on localhost but also any thing else. For example in my own environment I run on https://marp.mydevhost.mydomain (I have a wildcard cert and nginx forward that subdomain to the marpit server), but by doing so I lose the reloader functionality...
The text was updated successfully, but these errors were encountered:
It looks like the live reload of the marpit server always tries to connect to localhost. This doesn't work if you use a different hostname. Especially in the era of remote editing this is not uncommon. It would be nice if:
/live-reload-ws
)By doing so it would work on localhost but also any thing else. For example in my own environment I run on
https://marp.mydevhost.mydomain
(I have a wildcard cert and nginx forward that subdomain to the marpit server), but by doing so I lose the reloader functionality...The text was updated successfully, but these errors were encountered: