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
Hi, first of all thank you for writing this handy tool. It appears to be just what I need.
In order to get a feel for how both http-broadcast and mercure work I'm trying to run the supplied examples. Unfortunately both the Docker and Kubernetes examples don't appear to work correctly (or I'm doing something wrong 😄). I'm not familiar enough yet with mercure or your code to figure it out myself. I'd appreciate if you could point me in the right direction!
I'm using the unmodified demo code from the /examples dir. In both demos the mercure hub responds with 404 on every query. Of course this means that the Varnish cache never gets flushed.
Hello, mercure changed the default route from /hub to /.well-known/mercure and I didn't updated http-broadcast documentation. I think this is the route cause of your issue.
Could you give a try with HUB_ENDPOINT=http://hub_container_name/.well-known/mercure?
If it's OK, I'll really appreciate if you had time to open a PR.
Hi, first of all thank you for writing this handy tool. It appears to be just what I need.
In order to get a feel for how both http-broadcast and mercure work I'm trying to run the supplied examples. Unfortunately both the Docker and Kubernetes examples don't appear to work correctly (or I'm doing something wrong 😄). I'm not familiar enough yet with mercure or your code to figure it out myself. I'd appreciate if you could point me in the right direction!
I'm using the unmodified demo code from the
/examples
dir. In both demos the mercure hub responds with 404 on every query. Of course this means that the Varnish cache never gets flushed.Docker-compose:
Kubernetes:
mercure deployment
varnish deployment
The text was updated successfully, but these errors were encountered: