Release: attach the console's files for a host install #106

Merged
jcoffey-dev merged 1 commits from ci/release-files into main 2026-10-12 18:27:12 +00:00
Owner

For the installer's --console host (phase 2). A release tag's GitHub run gets a new files job, after publish:

  • It takes /usr/share/nginx/html out of the amd64 image that was just published, so it's exactly what the image serves, not a second build.
  • It attaches inbuxa-admin.tar.gz and SHA256SUMS to the Gitea release. Static files are the same on every architecture, so there's one tarball.
  • index.html keeps the image's api-base-url tag, and the installer sets it the way the entrypoint does.
  • A re-run replaces the assets. Uploads use HTTP/1.1 with retries, like the server's binaries. The job feeds report.

Checked locally: extracting the 2026.10.12 image this way gives a 3.4 MB tarball with index.html, assets/, sieve-playground/ and so on. actionlint is clean for this job (its one warning is in the existing github-release job). It takes effect on the next release tag.

For the installer's `--console host` (phase 2). A release tag's GitHub run gets a new `files` job, after `publish`: - It takes `/usr/share/nginx/html` out of the amd64 image that was just published, so it's exactly what the image serves, not a second build. - It attaches **`inbuxa-admin.tar.gz`** and **`SHA256SUMS`** to the Gitea release. Static files are the same on every architecture, so there's one tarball. - `index.html` keeps the image's `api-base-url` tag, and the installer sets it the way the entrypoint does. - A re-run replaces the assets. Uploads use HTTP/1.1 with retries, like the server's binaries. The job feeds `report`. Checked locally: extracting the 2026.10.12 image this way gives a 3.4 MB tarball with `index.html`, `assets/`, `sieve-playground/` and so on. actionlint is clean for this job (its one warning is in the existing `github-release` job). It takes effect on the next release tag.
jcoffey-dev added 1 commit 2026-10-12 18:04:36 +00:00
Release: attach the console's files for a host install
ci / build (pull_request) Skipped
ci / publish (pull_request) Skipped
ci / notices (pull_request) Successful in 12s
github/ci (branch) GitHub Actions
ci / github (pull_request) Successful in 1m35s
52cda0f579
A release tag's run now also takes the console's files out of the image it just published and attaches them to the Gitea release as inbuxa-admin.tar.gz, with SHA256SUMS: what the installer's --console host unpacks and a web server on the host serves. They are static files, the same for every architecture, so one tarball. index.html keeps the image's api-base-url tag for the installer to set, as the image's entrypoint does. A re-run replaces the assets; uploads go over HTTP/1.1 with retries, as the server's binaries do. Its result feeds the report to Gitea.
jcoffey-dev merged commit e44e5ee9c1 into main 2026-10-12 18:27:12 +00:00
jcoffey-dev deleted branch ci/release-files 2026-10-12 18:27:12 +00:00
Sign in to join this conversation.