-
Notifications
You must be signed in to change notification settings - Fork 108
WAN Getting Started improvements #1836
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
base: v/5.5
Are you sure you want to change the base?
Conversation
* More details on the docker network * added port info to the members * added a docker name to make these easier to identify within docker * enabled CLC/Console in both * More instructions on IP addresses (more details in the logged info) * changed the startup docker command for tokyo cluster as the paths were not working * added an example using CLC to check the data on the passive cluster * clean up instructions on how to remove the docker network
✅ Deploy Preview for hardcore-allen-f5257d ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
docker run \ | ||
-p 5701:5701 \ | ||
--name hazelcast-london \ | ||
--network hazelcast-network \ |
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.
remove to avoid container name clashes
docker run \ | ||
--network hazelcast-network \ | ||
-e JAVA_OPTS="-Dhazelcast.config=/opt/hazelcast/config_ext/hazelcast.yaml" -v ~/config-tokyo:/opt/hazelcast/config_ext hazelcast/hazelcast-enterprise:{ee-version} | ||
--name hazelcast-tokyo \ |
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.
remove to avoid container name clashes
@oliverhowell Is this PR now out of date? |
It was always going to clash with #1784 anyway but I've pulled the changes in so it's fine. I'll close this when I merge my master PR. |
This needs testing