Better release structure

[adyanth]

Would you be able to add each file to the release (through a CI pipeline) instead of a zip file with everything? That is standard practice (e.g. k3s), and makes it easier for scripts to pull them (for example, in a docker image) without downloading everything.

To take it further, would you be willing to release scratch docker images with the static binaries as the entry point in each architecture supported by the linux binaries to your repo CI pipeline to make it official, instead of linking to https://github.com/1activegeek/docker-airconnect?

I can definitely submit PRs for this if you think this is something you would want to see.

[adyanth]

FROM ubuntu:latest AS build
ARG CANDIDATE
RUN apt update && apt install -y build-essential
WORKDIR /airconnect
RUN --mount=type=bind,target=.,rw chmod +x *.sh && ./buildall.sh "$CANDIDATE" && mv bin /output


FROM scratch
COPY --from=build /output/*-static /

Build with:

docker build --platform linux/amd64 --build-arg CANDIDATE=x86_64-linux-gnu-gcc  -t image:tag .

Something like this ^ and then run with:

$ docker run --rm image:tag /airupnp-linux-x86_64-static
[04:08:11.677] main:1386 Starting airupnp version: v1.9.3 (Jan  4 2026 @ 04:04:51)
[04:08:11.680] main:1393 no config file, using defaults
[04:08:11.742] Start:1094 Binding to iface 192.168.215.4:0 [eth0]
[04:08:11.744] Start:1133 Starting pico HTTP server on port 43797
^C[04:08:12.956] Stop:1164 terminate update thread ...
[04:08:12.957] Stop:1169 flush renderers ...
[04:08:12.957] Stop:1172 terminate libupnp
[04:08:13.464] Stop:1191 terminate main thread ...

[philippe44]

Thanks but I can't do CI as I have too many variants of OS and CPU that I had to rebuild cross-compilers for many of them, you can't just install such compilers from a docker instance.

[adyanth]

Do you have the steps documented that you use to generate the zip file?

[philippe44]

It's just zipping what the build scripts put into a ./bin directory, so nothing fancy