This PR adds scripting support to be able to launch multiple discrete Docker projects with different Provider configurations, simultaneously.
start.sh now takes an (optional) argument:
-n <project-name>: base name to use for both the saved environment file & Docker compose project
saved environment files go in ${HOME}/.projectliberty directory
Example
Spin up Gateway instance for Provider A ./start.sh -n providerA
will use env file `${HOME}/.projectliberty/.env.providerA
Docker COMPOSE_PROJECT_NAME is "providerA"
Spin up Gateway instance for Provider B ./start.sh -n providerB
will use env file `${HOME}/.projectliberty/.env.providerB
Docker COMPOSE_PROJECT_NAME is "providerB"
This will start up 2 separate Gateway projects in Docker: gateway-provider-A and gateway-provider-B, each with their own set of services, dedicated port ranges, private internal Docker network, etc.
The start.sh script will prompt for port ranges to allocate local ports that won't conflict across the projects.
Purpose
This PR adds scripting support to be able to launch multiple discrete Docker projects with different Provider configurations, simultaneously.
start.shnow takes an (optional) argument:-n <project-name>: base name to use for both the saved environment file & Docker compose project${HOME}/.projectlibertydirectoryExample
./start.sh -n providerACOMPOSE_PROJECT_NAMEis "providerA"./start.sh -n providerBCOMPOSE_PROJECT_NAMEis "providerB"This will start up 2 separate Gateway projects in Docker:
gateway-provider-Aandgateway-provider-B, each with their own set of services, dedicated port ranges, private internal Docker network, etc.The
start.shscript will prompt for port ranges to allocate local ports that won't conflict across the projects.