Skip to content

SynxDB CE

Install SynxDB CE

After downloading your RPM or DEB from the signup email, follow these steps to verify the signature and install. Every SynxDB CE package is GPG-signed; verification is optional but strongly recommended for any production-bound install.

1. Download the public key

Fetch the armored key from https://www.synxdata.com/keys/synxdb-ce.asc, then confirm its fingerprint matches what your signup email shows. The fingerprint is the trust anchor, if the value gpg --show-keys reports differs from the email, do not import the key.

# Download the SynxDB CE public signing key
curl -O https://www.synxdata.com/keys/synxdb-ce.asc

# Confirm the fingerprint matches what's in your signup email
gpg --show-keys synxdb-ce.asc | awk '/^ /{print; exit}'
# Expected: A965 E32F 0312 ECAF EC26  831E 72B2 635D 204E 5473

On a minimal Rocky 9 install, gpg is provided by the gnupg2 package: sudo dnf install -y gnupg2.

2a. Verify on Rocky Linux 9 / RHEL 9 (RPM)

Import the key into the system's RPM keyring, then ask rpm to check the package signature.

# Install the key into the system RPM keyring
sudo install -m 644 synxdb-ce.asc /etc/pki/rpm-gpg/RPM-GPG-KEY-synx-community
sudo rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-synx-community

# Confirm the key landed in the keyring
rpm -q gpg-pubkey --qf '%{summary}\n' | grep -i synx
# Expected: Cloudsmith Package (synx/community) <[email protected]> public key

# Verify the package signature
rpm --checksig synxdb-ce-*.rpm
# Expected: synxdb-ce-...rpm: digests signatures OK

2b. Verify on Ubuntu 22.04 LTS (DEB)

Import the key into a dedicated keyring, then verify the .deb with dpkg-sig.

# Install the verifier (one-time)
sudo apt-get update
sudo apt-get install -y dpkg-sig gnupg

# Import the key into a dedicated keyring
sudo gpg --no-default-keyring --keyring /usr/share/keyrings/synx-community.gpg \
  --import synxdb-ce.asc

# Confirm the fingerprint matches
gpg --no-default-keyring --keyring /usr/share/keyrings/synx-community.gpg \
  --list-keys --fingerprint
# Expected fingerprint: A965 E32F 0312 ECAF EC26  831E 72B2 635D 204E 5473

# Verify the package signature
dpkg-sig --verify synxdb-ce_*.deb
# Expected: GOODSIG _gpgbuilder 72B2635D204E5473 ...

3a. Install on Rocky Linux 9 / RHEL 9

SynxDB CE depends on a handful of packages that ship through EPEL (xerces-c) and the CodeReady Linux Builder repo (perl-IPC-Run). Both are part of the Rocky / RHEL ecosystem but are not enabled by default on a fresh install, enable them once, then dnf install resolves everything from there.

# Enable EPEL (for xerces-c) and CRB (for perl-IPC-Run)
sudo dnf install -y epel-release dnf-plugins-core
sudo dnf config-manager --set-enabled crb

# Install the verified RPM
sudo dnf install -y ./synxdb-ce-*.rpm

# Confirm
rpm -qi synxdb-ce

On RHEL 9 the equivalent of CRB is named codeready-builder-for-rhel-9-x86_64-rpms, enable with subscription-manager repos --enable instead of dnf config-manager.

3b. Install on Ubuntu 22.04 LTS

All runtime dependencies resolve from the default main and universe repositories that ship with Ubuntu 22.04, no extra repos to enable.

# Install the verified DEB (apt resolves runtime deps from main + universe)
sudo apt-get update
sudo apt-get install -y ./synxdb-ce_*.deb

# Confirm
dpkg -s synxdb-ce | head

If verification fails

  • "NOT OK" or "BAD signature", do not install the package. The file was modified, the wrong key was imported, or the download was corrupted. Re-download from your signup email and try again. If it still fails, email [email protected].
  • "MISSING KEYS" / "key not found", the key didn't import. Re-run the import step and confirm with the rpm -q gpg-pubkey or gpg --list-keys check above.
  • Different fingerprint reported, do not install. The fingerprint above is the only one that signs SynxDB CE. Email [email protected] with the fingerprint you saw.