-
Notifications
You must be signed in to change notification settings - Fork 73
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docs(sandbox): update-sandbox-docker-compose (#246)
Update sandbox docker-compose.yml and docs gh-244
- Loading branch information
1 parent
98fdb0f
commit b967ee7
Showing
3 changed files
with
52 additions
and
23 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,23 +1,30 @@ | ||
# Sandbox Examples | ||
The sandbox examples have been preconfigured with a `docker-compose` file for easy setup. Please examine the environment variables in the file prior to running and change the variables where appropriate. For example, if you want to test the Keycloak integration, plugin your configuration values to the `docker-compose.yml` file. | ||
The sandbox examples have been pre-configured with a `docker-compose` file for easy setup. Please examine the environment variables in the file prior to running and change the variables where appropriate. For example, if you want to test the Keycloak integration, plugin your configuration values to the `docker-compose.yml` file. | ||
|
||
## Basic Setup | ||
You must have `docker-compose` installed locally. This is not a production grade setup. | ||
|
||
To start the services, simply run from this directory. | ||
```shell | ||
docker-compose up | ||
docker-compose up --build | ||
``` | ||
|
||
If you would like the services to run in detached mode, supply the `-d` parameter. | ||
|
||
The services are now running under the following: | ||
* [notification-example](http://localhost:3030) | ||
* [auth-multitenant-example](http://localhost:3000) | ||
* [audit-ms-example](http://localhost:3032/explorer) | ||
* [notification-example](http://localhost:3030/explorer) | ||
* [auth-multitenant-example](http://localhost:3000/explorer) | ||
* [in-mail-example](http://localhost:3033/explorer) | ||
* [notification-socket-example](http://localhost:3030/explorer) | ||
* [scheduler-example](http://localhost:3034/explorer) | ||
* [video-conferencing-ms-example](http://localhost:3040/explorer) | ||
* [workflow-ms-example](http://localhost:3031/explorer) | ||
* [Camunda](http://localhost:8080) | ||
* [pgAdmin](http://localhost:5050) | ||
* PostgreSQL - localhost:5432 | ||
* Redis - localhost:6739 | ||
|
||
Credentials for the database and pgAdmin are in the `docker-compose` file or can be overridden with environment variables. An orchestration container also runs that creates two databases: `notification_db` and `authentication_db`. You will still need to run the database migrations yourself. | ||
Credentials for the database and pgAdmin are in the `docker-compose` file or can be overridden with environment variables. An orchestration container creates all of the databases and another runs the service DB migrations for you. | ||
|
||
When connecting to PostgreSQL or from within one of the containers, pay attention to the network and service name defined in the `docker-compose` file, since you will connect via the Docker network and service name. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters