No moving targets.
The installer targets a published version instead of a moving development branch.
verified bytes in // owned runtime out
Bootstrap the box.
Keep root.
Download signed binaries, inspect the procedure, and initialize a plain Docker Compose project on your Linux server. No web account, no remote installer state, no surprise phone-home ceremony.
SDBX-BOOTSTRAP(1) :: TRUST NOTHING, VERIFY BYTES
Fast command.
Paranoid pipeline.
The installer downloads one tagged release, checks it, stages both binaries, and keeps a rollback path. Convenience is not permission to skip verification.
Trust the signatures.
Signatures and checksums confirm that the downloaded archive matches the published release.
Run before replace.
SDBX validates the CLI and local dashboard service before touching their final locations.
Swap or roll back.
If the final replacement fails, the installer restores the previous working binaries.
SYNOPSIS :: PIPE TO EYES BEFORE SHELL
Save. Read. Then execute.
This command appears only when the verified deployment contract marks the repository, release, installer, and private security intake as available.
SDBX-BOOTSTRAP(1) :: BUILD THE BYTES YOURSELF
Build what
you inspected.
This tag-pinned route builds and installs the two binaries only. Use the release packaging and operations guide for the hardened systemd units and complete host integration.
version=v1.0.0-RC1
git clone --branch "$version" --depth 1 https://github.com/get-sdbx/sdbx.git
cd SDBX
test "$(git describe --tags --exact-match)" = "$version"
go mod verify
make build
sudo install -m 0755 bin/sdbx /usr/local/bin/sdbx
sudo install -m 0755 bin/sdbxd /usr/local/bin/sdbxd