Repository navigation
WolfProxy v0.4.15
v0.4.15: scaffold a default nginx tree when none exists
klasSponsor installed wolfproxy WITHOUT nginx, so /etc/nginx had no
config files or site structure at all — wolfproxy came up with zero
sites and behaved oddly.
ensure_nginx_scaffold() now lays down a minimal standard nginx tree when
the config dir has no usable configuration (no root.conf, nothing in
sites-enabled/, no *.conf in conf.d/): creates conf.d/, sites-available/,
sites-enabled/, a default web root (/var/www/html) with a landing page,
and a default catch-all HTTP site on :80 (sites-available/default +
sites-enabled/default). Runs at startup before the config load.
NEVER overwrites: it bails the moment any existing config is detected,
and every individual write is existence-guarded, so an install that
already has nginx files is untouched (Golden Rule). Best-effort and
non-fatal — a write failure is logged and wolfproxy still starts.
Tests: scaffolds_a_loadable_default_site_when_empty (round-trips the
default site through the real load_nginx_config and asserts a usable
HTTP:80 server + idempotency) and never_touches_an_existing_config.
Also smoke-tested the live binary against an empty config dir. clippy-clean.
Verifying this release
Each binary is signed via cosign keyless OIDC and ships with a SLSA build provenance attestation.
Verify the cosign signature:
cosign verify-blob \
--bundle wolfproxy-x86_64.cosign.bundle \
--certificate-identity-regexp 'https://github.com/wolfsoftwaresystemsltd/wolfproxy/\.github/workflows/release\.yml@.*' \
--certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
wolfproxy-x86_64
Verify the build provenance:
gh attestation verify wolfproxy-x86_64 --repo wolfsoftwaresystemsltd/wolfproxy
Verify the SHA-256 checksum:
sha256sum -c SHA256SUMS
Artifacts
wolfproxy-x86_64/wolfproxy-aarch64— static musl binaries (Linux x86_64 and ARM64).wolfproxy-<arch>.cosign.bundle— cosign signature bundle (cert + signature + Rekor entry).SHA256SUMS— checksums for both binaries.