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.
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
For the installer's
--console host(phase 2). A release tag's GitHub run gets a newfilesjob, afterpublish:/usr/share/nginx/htmlout of the amd64 image that was just published, so it's exactly what the image serves, not a second build.inbuxa-admin.tar.gzandSHA256SUMSto the Gitea release. Static files are the same on every architecture, so there's one tarball.index.htmlkeeps the image'sapi-base-urltag, and the installer sets it the way the entrypoint does.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 existinggithub-releasejob). It takes effect on the next release tag.