docs: align release artifact docs

This commit is contained in:
Ragnor Comerford 2026-05-29 14:03:59 +02:00
parent 1a4d2cee97
commit 50910b3753
No known key found for this signature in database
3 changed files with 5 additions and 6 deletions

View file

@ -140,9 +140,9 @@ The server binary ships in two flavors:
| **Default** (on-prem / local dev) | `cargo build --release` | Core server, no AWS SDK |
| **AWS** | `cargo build --release --features aws` | Adds AWS Secrets Manager backend for bearer tokens |
Release artifacts are published with matching suffixes —
`omnigraph-server-<version>-<platform>.tar.gz` for the default build and
`omnigraph-server-<version>-<platform>-aws.tar.gz` for the AWS-enabled build.
Tagged release archives contain the default `omnigraph` and
`omnigraph-server` binaries. AWS-enabled server binaries are built from source
with `cargo build --release --features aws -p omnigraph-server` when needed.
The AWS build adds ~150 transitive deps and ~30-60s of first-build compile
time. Default builds don't pay that cost.

View file

@ -78,7 +78,6 @@ install -m 0755 target/release/omnigraph-server ~/.local/bin/omnigraph-server
Tagged releases are expected to publish:
- `omnigraph-linux-x86_64.tar.gz`
- `omnigraph-macos-x86_64.tar.gz`
- `omnigraph-macos-arm64.tar.gz`
Each archive contains both binaries: