v3.8.2

Images

ghcr.io/caddyproxymanager/web:3.8.2
ghcr.io/caddyproxymanager/caddy:3.8.2
ghcr.io/caddyproxymanager/agent:3.8.2

Published by the image build this release starts; give it a few minutes. The
docker-compose.yml in the archive below already names these tags, so what you
deploy from it stays on this release until you choose to move -- but it also means
a docker compose pull run before the build finishes has nothing to fetch.

Deployment files

A clone of CaddyProxyManager/deploy upgrades with
git pull && docker compose pull && docker compose up -d.

Unchanged since v3.8.1. Pulling the images is enough.

caddy-proxy-manager-v3.8.2-deploy.tar.gz is ready to run as it unpacks: extract it
into one directory and docker compose up -d works without moving anything. Its one
subdirectory, docker/caddy/, is Caddy's build context, which Settings -> Caddy build
rebuilds from. It includes the managed CrowdSec container, which stays off
until Settings -> CrowdSec turns it on. Its docker-compose.yml differs from the
copy in the repository in exactly two ways: it mounts its files from beside itself
rather than from ./docker/, and it pins the three images to 3.8.2 rather
than latest.
The repository copy follows latest on purpose; this one is a snapshot of one
release and says so.

Installing without internet access

The image build attaches an air-gap bundle per architecture before this release is published:
-airgap-<web|caddy|agent>.tar.gz hold our images, -airgap-deploy.tar.gz the
deployment files and a load script, and the signed -airgap-manifest.txt their
checksums and the third-party images to bring in by digest. See
https://caddyproxy.com/start/offline/.

Changes

• chore(release): 3.8.2 (9c6f039)

Full diff: v3.8.1...v3.8.2