Deployment

Quick Start

Blaze can be started with a single command using docker:

docker run -d --name blaze -p 8080:8080 samply/blaze:{{ tag }}@{{ digest }}

Verification

For container images, we use cosign to sign images. This allows users to confirm the image was built by the expected CI pipeline and has not been modified after publication.

::: code-group

cosign verify "samply/blaze:{{ tag }}@{{ digest }}" \
  --certificate-identity-regexp "https://github.com/samply/blaze/.*" \
  --certificate-oidc-issuer "https://token.actions.githubusercontent.com" \
  --certificate-github-workflow-ref="refs/tags/{{ release }}" \
  -o text >/dev/null

cosign verify "samply/blaze-frontend:{{ tag }}@{{ frontendDigest }}" \
  --certificate-identity-regexp "https://github.com/samply/blaze/.*" \
  --certificate-oidc-issuer "https://token.actions.githubusercontent.com" \
  --certificate-github-workflow-ref="refs/tags/{{ release }}" \
  -o text >/dev/null

:::

The expected output is:

::: code-group

<<< @/cosign-verify.txt {text} [backend] <<< @/cosign-verify-frontend.txt {text} [frontend]

:::

This output ensures that the image was built by the GitHub Actions workflow of the repository samply/blaze and tag {{ release }}.

Production

For production-ready deployments, there are three options:

• Frontend and Backend Standalone
• Standalone Backend Only
• Distributed Backend Only

Configuration

Configuration is based on environment variables and documented in the Configuration section.