Note: Make sure all infrastructure containers are running, see docker-compose-infra directory.
To startup Kafka, MongoDB, Elasticsearch and Kibana, follow the steps below:
- Create a directory called
exec
inside thedocker-compose-cross-cutting
(this) directory, and go to that directory.
This exec
directory is ignored by gitignore, so can't be pushed to GitHub.
mkdir exec
cd exec
- Create the following directories as children of the
docker-compose-cross-cutting/exec
directory:
data
mkdir {data}
- Create the following directories as children of the newly created
data
directory:
- authentication-svc
- authorization-svc
- platform-configuration-svc
- auditing-svc
- logging-svc
mkdir {data/authentication-svc,data/authorization-svc,data/platform-configuration-svc,data/auditing-svc,data/logging-svc}
Note: For Mac users you might have to grant full access to these directories, to do that execute in the exec directory:
sudo chmod -R 777 data
- Copy the
.env.sample
to the exec dir:
cp ../.env.sample ./.env
- Review the contents of the
.env
file. If using MacOS update the ROOT_VOLUME_DEVICE_PATH to reflect the absolute path
Start the docker containers using docker compose up (in the exec dir)
docker compose -f ../docker-compose-cross-cutting.yml --env-file ./.env up -d
# OR for older versions of docker
docker-compose -f ../docker-compose-cross-cutting.yml --env-file ./.env up -d
To view the logs of the infrastructure containers, run:
docker compose -f ../docker-compose-cross-cutting.yml --env-file ./.env logs -f
# OR for older versions of docker
docker-compose -f ../docker-compose-cross-cutting.yml --env-file ./.env logs -f
To stop the infrastructure containers, run:
docker-compose -f ../docker-compose-cross-cutting.yml --env-file ./.env stop
# OR for older versions of docker
docker-compose -f ../docker-compose-cross-cutting.yml --env-file ./.env stop