-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove unnecessary mention of ServicePulse #106
Conversation
@@ -6,10 +6,11 @@ This showcase consists of 4 processes hosting MassTransit message producers and | |||
|
|||
## Launching the Showcase in Docker | |||
|
|||
The showcase requires a connection to a broker (by default RabbitMQ), [ServiceControl](https://hub.docker.com/r/particular/servicecontrol) container, [ServicePulse](https://hub.docker.com/r/particular/servicepulse) container and the [MassTransit Connector for ServiceControl](https://hub.docker.com/r/particular/servicecontrol-masstransit-connector) container. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My opinion is that we still need this list of required containers, so that if someone is having an error in the showcase they can see what is in docker and understand what each container is there for
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, but I think if we put that under the docs, that would probably be a better place for them. I can't see a good enough reason to keep them this prominent on the Readme.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I put them under the troubleshooting section now.
As we don't want people to focus on names like ServicePulse or ServiceControl unnecessarily, preferring to keep the focus on the Service Platform.