Viktor Vsk
Viktor Vsk
Hey @viktorvsk thanks, thats definitely a much cleaner way to handle this. And given its already documented probably this issue could be closed
Is there any followup info perhaps?
@Nathy-bajo last time I checked, a month or two ago, it didn't
I face the same issue when deploying with 3.1.x docker-compose. If I `docker-compose up` the default compose from the site on my host and connect to it with `pulsar://127.0.0.1:6650` it...