The binaries live here. The source code does not. The tool repos are private while their open-sourcing rounds finish, which used to mean binaries traveling by Slack attachment, a distribution model with all the version control of a flash drive taped to a pigeon. This is the fix: every release lands here automatically, published by CI instead of vibes.
For ssdg 1.9.0 and newer, the binary follows a floating image tag: ssdg --pull fetches the latest minor/patch release and that is the whole upgrade. No need to remove local images; the pull just moves the tag.
Binaries older than 1.9.0 pin their own image version forever, so --pull on them keeps downloading the same old image. If that is you, download the current binary from this page once and the floating model takes over from there. A new MAJOR version also means a new binary, and the dashboard will tell you so.
| Tool | What it does | Tag prefix |
|---|---|---|
| ssdg (SafeShift Doc Gen) | Point it at an OpenShift cluster (or a must-gather) and get a professional, sanitized cluster document in about a minute | ssdg-v* |
| ovtools | OpenShift virtualization tooling | ovtools-v* |
| rvtma | Report and visualization tooling | rvtma-v* |
Grab the latest release for your tool from the releases page. Each release ships binaries for macOS (arm64/amd64), Linux (arm64/amd64), and Windows. Yes, all five, every time, built by the same pipeline. The days of "can you send me the mac one again" are over.
For ssdg, make it executable and put it on your PATH:
chmod +x ssdg-darwin-arm64
sudo mv ssdg-darwin-arm64 /usr/local/bin/ssdgThe container images are already public: ghcr.io/elastocera/safeshift-doc-gen, with a mirror at quay.io/elastocera/ssdg for networks that block ghcr.io. The ssdg binary finds them on its own; you only care about this if your network has opinions.
Colleagues kept getting binaries over Slack, which works right up until you need to know which version anyone is actually running. Ask me how I know. This repo is the single distribution point, and the release tag is the answer to "which build do you have".
No code lives here, so resist the urge to open issues about bugs. The tools have homes; this is just the loading dock.