Getting started
Guides and examples
Reference documentation
Background concepts
Frequently Asked Questions
Integrations
The .release.yaml file
Customize how your application is built and run
Release will look for a
.release.yaml file to help inform how to build and run your application. The file .release.yaml must be in the root of the repository.Define the Docker Compose file
Here's how to define the Docker Compose file to use in Release:
1
compose: docker-compose.extended.yml
Copied!
Define a directory of raw Kubernetes manifests
Release allows you to define a directory of raw Kubernetes manifests that will be applied to each namespace. Release will adjust the namespace defined in each of the manifests to allow your services to run alongside whatever you have defined in the Kubernetes manifests.
1
manifests: k8s/manifests
Copied!
Build and deploy a static service
You can define how to build and deploy a static service or a Docker container not defined in your
docker-compose file, for example, here we define a JavaScript static build:1
builds:
2
- name: frontend
3
build_base: my-app
4
build_command: yarn build
5
build_output_directory: build
6
static: true
Copied!
Build a base Docker image
You might have a base Docker image that your
docker build depends on. The .release.yaml file allows you to define additional builds that live outside of your Docker Compose.1
builds:
2
- name: base
3
build:
4
context: dockerfiles/base
5
dockerfile: Dockerfile-base
6
target: web
Copied!