~ knotless Search/
↑↓ move↵ open⇧↵ all results

socialweb.computer/socialweb-computer-kcp

socialweb.computer: a compute market on atproto (kcp)

1 collaborator
0
0
51 lines · 2.5 KB Raw History
# How a release reaches prod

Only CI builds and deploys. A push to `main` of `knotless://socialweb.computer/socialweb-computer-kcp` runs:

1. `release`: the checks (`deploy/check.sh --fast`, this docs checker included), the one build, `main/<sha>/` and
   `main/latest/` in the bucket
2. `test`: the staging gate, one staging network, after `release`
3. `promote`, after `test` passed: moves channel `rc`, deploys the gateway, waits for every rc bidder, runs the prod gate, then copies
   `main/<sha>/` to `releases/<version>/` and moves channel `stable`; a failure moves `rc` back

The workflows: `.knotless/workflows/`; the pipeline: [plans/0040-release-pipeline.md](plans/0040-release-pipeline.md).

## Where each channel is

```sh run=gate
D=did:plc:gmlkrhimoueejcertevr4hl3
P=$(curl -fsSL https://plc.directory/$D | jq -r '.service[] | select(.id == "#atproto_pds") | .serviceEndpoint')
for c in stable rc; do
  curl -fsSL "$P/xrpc/com.atproto.repo.getRecord?repo=$D&collection=software.release.channel&rkey=socialweb-computer:$c" \
    | jq -r '"\(.value.name) \(.value.version.uri | sub(".*:"; ""))"'
done
```

You see `stable v0.0.0` and `rc v0.0.0-rc186` (2026-11-18). Bidders follow their channel and upgrade themselves
([bidder.md](bidder.md#upgrade-rollback-self-update)). The records and how they are followed: [protocol/release.md](protocol/release.md).

## The runs of a commit

```sh
export KNOTLESS_APPVIEW=https://knotless.socialweb.computer
knotless run list knotless://socialweb.computer/socialweb-computer-kcp --ref refs/heads/main | head -12
```

One line per workflow run: `success|failure|running <workflow> refs/heads/main <sha> <time>`. A failed run:
[ci-debug.md](ci-debug.md).

## What survives a deploy

| deploy | survives |
| --- | --- |
| gateway upgrade (`scripts/deploy.sh` on an installed gateway) | the state dir, kcp objects, the root OpenBao, the requester's DID and association, web sessions, running units |
| bidder upgrade (`upgrade --binary --sha256`, or its self-update) | the state dir, OpenBao, the bidder DID, handle, association, PDS repo, VMs |
| fresh install, or a lost state dir | nothing: a new DID, which needs its association again |

Nothing else is promised: a release may drop sessions, VMs, clusters or receipts.

## Roll back

A bidder, as its account: `rollback` ([bidder.md](bidder.md#upgrade-rollback-self-update)). The gateway, as its account:
`socialweb-computer rollback --state-dir /var/lib/socialweb-computer/socialweb`. A failed `promote` already moves `rc`
back; the next green `promote` rolls forward.