From bf8b5ace004b3b3c4141af893d85695ac2698f25 Mon Sep 17 00:00:00 2001 From: Mauro Mugnaini Date: Mon, 26 Oct 2020 12:44:18 +0000 Subject: [PATCH] README.md edited online with Bitbucket --- README.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 3da5f05..3101804 100644 --- a/README.md +++ b/README.md @@ -14,20 +14,22 @@ The Docker Compose Swarm files are present in the `stack` folder. ## Documentation The provided Docker stack files provide the following configuration: + - 4 Dynomites nodes (2 shards with 1 replication each one, handled by Dynomite directly) based on `autodynomite` image that is backed by Redis DB in the same container - 2 Conductor Server nodes with 2 replicas handled by Swarm - 2 Conductor UI nodes with 2 replicas handled by Swarm - 1 Elasticsearch node Build the Docker `autodynomite` image with the `Dockerfile` present in the dynomite folder and launch the three Docker Compose Swarm files is sequence: + - dynomite-swarm.yaml - elasticsearch-swarm.yaml - conductor-swarm.yaml The command to be executed should looks like: `docker stack deploy -c dynomite-swarm.yaml -c elasticsearch-swarm.yaml -c conductor-swarm.yaml [your stack name]` -If you plan to deploy more than 4 nodes for dynomite you should modify the `dynomite-swarm.yaml` and the `seeds.list` files as per your needs. -The `conductor-swarm-config.properties` should be let unmodified. +If you plan to deploy **more than 4 nodes** for dynomite persistence you should modify the `dynomite-swarm.yaml` and the `seeds.list` files as per your needs. +The `conductor-swarm-config.properties` should be left unmodified. ## Change log