ci: build and publish the image on every push to main

The registry account available on the testnet hosts is pull-only (403 on a blob upload even for an existing repository), so publishing goes the same way every other BitDeals image does: the Gitea runner builds and pushes with the CI credentials. Tags mirror the family — an immutable <version>.<sha7>, a moving <version>, and :latest for compose and Watchtower. The version is read out of the Dockerfile ARG rather than repeated here: a tag that can disagree with the binary inside is worse than no tag.
2026-08-06 12:01:10 +00:00
parent bf2c2d3508
commit 3a52b5128b
3 changed files with 58 additions and 0 deletions
@@ -66,6 +66,11 @@ docker run --rm -v btcdata:/data/.bitcoin registry.bitdeals.org/bitcoind -reinde

 ## build and publish

+A push to `main` builds and publishes the image (`.gitea/workflows/build.yaml`),
+tagging it three ways: `<version>.<sha7>` to deploy by, `<version>` to read, and
+`latest` for compose and Watchtower. By hand, when the registry credentials are
+at hand:
+
 ```sh
 docker build . --file docker/Dockerfile --tag registry.bitdeals.org/bitcoind
 docker push registry.bitdeals.org/bitcoind