Vyomi v2.0.9.1

Patch — fix the docker-compose-only install (caddy crash-looped for every fresh user).

Fixed

• Caddy no longer breaks docker compose up / --profile full. The caddy TLS sidecar was in profiles: ["tls", "full"], so the documented --profile full up -d started it — but the bare docker-compose install never lays down packaging/caddy/Caddyfile or TLS certs (Step 2 only fetches docker-compose.yml + .env). Docker then auto-created the missing Caddyfile path as an empty directory and the bind-mount failed (not a directory: are you trying to mount a directory onto a file), crash-looping caddy. Caddy is now profiles: ["tls"] only — opt-in. Plain installs run on http://localhost:9000 with zero extra files; HTTPS on :9443 is opt-in via docker compose --profile tls up -d (once a Caddyfile + cert/key are provided) or the vyomi up launcher (which provisions both via mkcert). The launcher path is unaffected — it uses docker-compose.appliance.yml and starts caddy by name with seeded files.
• Documented install path now reaches "Appliance is Ready." Because the readiness banner counts all backends, the previous docker compose up -d (4 services, rest lazy) capped at 26%. Portal install steps now use docker compose --profile full up -d so every backend starts eagerly → readiness 100%.

---

Artifacts

• SHA256SUMS
• cloud-learn-0.1.0.tar.gz
• cloud-learn-2.0.9.1-1.noarch.rpm
• cloud-learn-2.0.9.1.tar.gz
• cloud-learn_2.0.9.1_all.deb

Docker image: docker pull vyomi/appliance:2.0.9.1
Install: curl -fsSL https://raw.githubusercontent.com/vyomi-cloud/appliance/main/install.sh | bash
SHA256 checksums: see SHA256SUMS in attached artifacts.