Development builds

Development builds are container images built from every push to main and tagged with the commit, for testing only and never for production.

Each push to main produces container images and cross-compiled binaries. Container images are multi-arch (amd64, arm64) and use the same distroless base image as official releases.

Container images

Images are on the GitHub Container Registry, tagged with the short commit hash of the build (e.g. main-abc1234): ghcr.io/aislopware/slopscale:main-<sha>

To find the latest available tag, check the GitHub Actions workflow or the GitHub Container Registry package page.

For example, to run a specific development build:

docker run \
  --name slopscale \
  --detach \
  --read-only \
  --tmpfs /var/run/slopscale \
  --tmpfs /tmp \
  --volume "$(pwd)/config:/etc/slopscale:ro" \
  --volume "$(pwd)/lib:/var/lib/slopscale" \
  --publish 127.0.0.1:8080:8080 \
  --publish 127.0.0.1:9090:9090 \
  --health-cmd "CMD slopscale health" \
  ghcr.io/aislopware/slopscale:main-<sha> \
  serve

See Running slopscale in a container for full container setup instructions.

Binaries are published with each release for Linux amd64, arm64 and armv7, statically linked so they run on any distribution. There are no macOS or FreeBSD binaries: build from source or use the Nix flake there. The main branch is not built into binaries, only into the container image above.

After downloading, make the binary executable and follow the standalone binary installation instructions for setting up the service.