Skip to content

Reference

The API, configuration and file formats. The Go API reference is on pkg.go.dev.

  • Command line: the verbs, what validate checks, and the exit codes.
  • launch.yaml: every key, its default and what is refused.

The image

registry.gitlab.com/phpboyscout/go/launch/launch holds the static binary alone, at /launch, so a Kubernetes image volume mounted at /opt/launch gives /opt/launch/launch. It carries no shell and no launch-nvml, which links the training image's glibc.

It isn't signed yet (go/launch#9). Pin it by digest.

The release archives

A release publishes launch_linux_amd64, launch_linux_arm64 and launch-nvml_linux_amd64, each a .tar.gz, with checksums.txt, at https://pkg.phpboyscout.uk/go/launch/<tag>/. launch-nvml links glibc, and its floor against training images is still an open question in the spec. checksums.txt.sig is a detached OpenPGP signature of checksums.txt, made with go/launch's release key: Launch Release Signing <launch-release@phpboyscout.uk>, fingerprint 989B 3292 6D77 DAAD 53BA 4937 544C BF6C CC83 BC4B. Its public half is keys/launch-release.asc in this repository, and WKD publishes the same key for that address.

To verify a download, fetch the key, check the signature, then check the archive against the signed checksums:

gpg --locate-external-keys launch-release@phpboyscout.uk
gpg --verify checksums.txt.sig checksums.txt
sha256sum --ignore-missing -c checksums.txt

gpg --verify must report a good signature from the fingerprint above. A different key, or a missing checksums.txt.sig, means the release isn't one go/launch published.