From 8f77fcbd1dd23282ff9746e728ad4a0ac1e8a63c Mon Sep 17 00:00:00 2001 From: sven4ask Date: Wed, 26 Sep 2018 10:14:26 +0200 Subject: [PATCH] Fix a few tables --- README.md | 10 +++++----- full-node/AWS Elastic Beanstalk/README.md | 10 +++++----- full-node/Docker compose/README.md | 12 ++++++------ 3 files changed, 16 insertions(+), 16 deletions(-) diff --git a/README.md b/README.md index f583676..b300630 100644 --- a/README.md +++ b/README.md @@ -14,11 +14,11 @@ _You can optain the latest version of `docker-compose` using pip._ This repository contains the configuration files to run your LTO Node. There are 3 configuration variations of the node. Each configuration serves a different need of the node: -|Node Type |Description| -|-----------------------------------|-----------| -|[Public Node only](public-node) | Contains only the public node. This configuration can be used for mining | -|[Anchor Node](anchor-node) | Contains both the public node and the anchoring service. This configuration can be used for the anchoring of hashes of the public LTO chain | -|[Full Node](full-node) | Contains all services. This configuration can used to run decentralized workflows | +Node Type |Description +-----------------------------------|----------- +[Public Node only](public-node) | Contains only the public node. This configuration can be used for mining +[Anchor Node](anchor-node) | Contains both the public node and the anchoring service. This configuration can be used for the anchoring of hashes of the public LTO chain +[Full Node](full-node) | Contains all services. This configuration can used to run decentralized workflows ### TestNet diff --git a/full-node/AWS Elastic Beanstalk/README.md b/full-node/AWS Elastic Beanstalk/README.md index cb2da57..76d58c8 100644 --- a/full-node/AWS Elastic Beanstalk/README.md +++ b/full-node/AWS Elastic Beanstalk/README.md @@ -27,9 +27,9 @@ Now your node is should good to go! The node configuration comes with Redis, RabbitMQ and MongoDB included. It is adviced to run these services outside of the node. The following Environment properties can be used to connect to external services: -| Service | Variable | Description | -| ------------------------- | ----------------------------| ------------------------------------- | -| LegelEvents / Legalflow | MONGODB_URL | Use the MongoDB connection string | -| Anchor | ANCHOR_REDIS_URL | Use the redis connection string | -| Event Dispatcher | DISPATCHER_RABBITMQ_CLIENT | Use the RabbitMQ connection string | +Service | Variable | Description +------------------------- | ----------------------------| ------------------------------------- +LegelEvents / Legalflow | MONGODB_URL | Use the MongoDB connection string +Anchor | ANCHOR_REDIS_URL | Use the redis connection string +Event Dispatcher | DISPATCHER_RABBITMQ_CLIENT | Use the RabbitMQ connection string diff --git a/full-node/Docker compose/README.md b/full-node/Docker compose/README.md index e73264f..5f85c39 100644 --- a/full-node/Docker compose/README.md +++ b/full-node/Docker compose/README.md @@ -48,12 +48,12 @@ or The node configuration comes with Redis, RabbitMQ and MongoDB included. It is adviced to run these services outside of the node. The following Environment properties can be used to connect to external services: -| Service | Variable | Description | -| ------------------------- | ----------------------------| ------------------------------------- | -| LegelEvents / Legalflow | MONGODB_URL | Use the MongoDB connection string | -| Anchor | ANCHOR_REDIS_URL | Use the redis connection string | -| Event Dispatcher | DISPATCHER_RABBITMQ_CLIENT | Use the RabbitMQ connection string | -| Webserver | PORT | Run the node on a different port | +Service | Variable | Description +------------------------- | ----------------------------| ------------------------------------- +LegelEvents / Legalflow | MONGODB_URL | Use the MongoDB connection string +Anchor | ANCHOR_REDIS_URL | Use the redis connection string +Event Dispatcher | DISPATCHER_RABBITMQ_CLIENT | Use the RabbitMQ connection string +Webserver | PORT | Run the node on a different port ### Running