docker-compose.yml
, package.json
, or .release.yaml
file to be in the root of your application's Git repository. Release uses these files to generate the Application Template that is used as a blueprint to build your environments.docker-compose.yaml
or package.json
files reside, you can add a .release.yaml
file to the root of your repository to tell Release where these files are located. See The .release.yaml
file reference guide for more information.docker-compose.yml
file that builds three Docker images and leverages two off-the-shelf containers for Redis and Postgres:docker-compose build
. Release looks for all services with a build
stanza, and executes a docker build for each service found.docker-compose
ports (HOST:CONTAINER
) definition to determine when a service should be exposed to the internet. When Release encounters a service with a HOST:CONTAINER
definition, it creates a NodePort, load balancer rule, and DNS hostname entry for the service.docker-compose
.docker-compose
as a starting point. All of the environment variables for each service defined in your docker-compose
are loaded into Release when you initially create an application. Release supports all of the standard docker-compose
mechanisms for defining environment variables.docker-compose
file: