Adding (v)host configurable for STOMP protocol #12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I found I had to configure the vhost of the STOMP connection in order to connect to a RabbitMQ server at Edinburgh.
I don't know if it's common/best-practice to have a vhost which is the IP of the host associated with the MQ (this is the default from the go library) but I'm aware of a few use-cases where this has not been the case in a setup, hence I've made it configurable.
I've just added a host parameter to the config so that it's picked up and passed onto RabbitMQ correctly. I think this is probably best as a string, but I can't think of a sensible default to add here other than the rabbitmq one of '/' if it's worth making this an optional config parameter.
Happy to change this to 'vhost' rather than 'host' if having this and a url might cause some confusion.