The .release.yaml file

Search…

Customize how your application is built and run

ReleaseHub 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 ReleaseHub:
compose: docker-compose.extended.yml
Define a directory of raw Kubernetes manifests
ReleaseHub allows you to define a directory of raw Kubernetes manifests that will be applied to each namespace. ReleaseHub 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.
manifests: k8s/manifests
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:
builds:
- name: frontend
  build_base: my-app
  build_command: yarn build
  build_output_directory: build
  static: true
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.
builds:
- name: base
  build:
    context: dockerfiles/base
    dockerfile: Dockerfile-base
    target: web

Reference documentation - Previous

GitOps

Next - Reference documentation

Docker Compose Conversion Support

Last modified 7d ago

Copy link

Outline

Define the Docker Compose file

Define a directory of raw Kubernetes manifests

Build and deploy a static service

Build a base Docker image