.release.yaml File

Release will look for a .release.yaml to help inform how to build and run your application. The file .release.yaml must be in the root of the repository.
1
compose: docker-compose.extended.yml
Copied!
In this example we define the docker-compose to use in Release
Release also 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 along side whatever you have defined in the kubernetes manifests.
1
manifests: k8s/manifests
Copied!
In this example we define a directory of raw kubernetes manifests
You can also define how to build and deploy a static service or a docker container not defined in your docker-compose.
1
builds:
2
- name: frontend
3
  build_base: my-app
4
  build_command: yarn build
5
  build_output_directory: build
6
  static: true
Copied!
In this example we define a javascript static build
You might have a docker base image that your docker builds depend on. The .release.yaml 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!
In this example we build a base docker image that will be used to build other docker images defined in this repository

Reference Guide - Previous

GitOps

Next - Reference Guide

Docker Compose Conversion Support

Last modified 1mo ago

Copy link