Deployment

Quick Start

Blaze can be started with a single command using docker:

docker run -d --name blaze -p 8080:8080 samply/blaze:1.0

Verification Since 1.0

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.

cosign verify "samply/blaze:1.0" \
  --certificate-identity-regexp "https://github.com/samply/blaze/.*" \
  --certificate-oidc-issuer "https://token.actions.githubusercontent.com" \
  --certificate-github-workflow-ref="refs/tags/v1.0.0" \
  -o text

The expected output is:

Verification for index.docker.io/samply/blaze:1.0 --
The following checks were performed on each of these signatures:
  - The cosign claims were validated
  - Existence of the claims in the transparency log was verified offline
  - The code-signing certificate was verified using trusted certificate authority certificates
Certificate subject: https://github.com/samply/blaze/.github/workflows/build.yml@refs/tags/v1.0.0
Certificate issuer URL: https://token.actions.githubusercontent.com
GitHub Workflow Trigger: push
GitHub Workflow SHA: 79937e53c48b5966bc8774feec98e1708980d73f
GitHub Workflow Name: Build
GitHub Workflow Repository: samply/blaze
GitHub Workflow Ref: refs/tags/v1.0.0

This output ensures that the image was build on the GitHub workflow on the repository samply/blaze and tag v1.0.0.

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.