Skip to content

WebCaller v0.16.1 — Prebuilt Docker installation

Pre-release
Pre-release

Choose a tag to compare

@adlererik adlererik released this 18 Oct 02:50
· 38 commits to main since this release

WebCaller now offers a ready-made Docker distribution alongside native Node.js and source-built Docker installations. The same Signal-like browser phone, encrypted disappearing chat/media, adaptive voice/video and optional call-verification words remain available.

New prebuilt installation

Download WebCaller-Docker-v0.16.1.tar.gz or .zip below. This small bundle downloads the selected ready-to-run images automatically; it does not contain the operating-system images itself. Verify the archive against SHA256SUMS.txt.

On a fresh supported Linux server with Docker Engine and Compose installed:

./webcaller setup
./webcaller start
./webcaller qr

The wizard asks for your own domain, HTTPS/Tunnel choice, TURN relay and optional ntfy alerts. It generates fresh private credentials; the first-phone QR avoids typing a long owner code. Invitees simply open their invitation and follow the phone guide.

Plain-language Docker guide · Source-built Docker · Native Node.js

Included services and updates

  • Native Linux amd64 and arm64 project images hosted publicly at ghcr.io/adlererik/webcaller, with versioned app, -setup and -turn variants. No GitHub login is required. Release bundles pin every project/upstream image by digest.
  • Containerized setup/QR tools and optional isolated ntfy, coturn, Caddy HTTPS or Cloudflare connector. No host Node/npm/Python installation is required for this package.
  • Separate persistent app, ntfy-state and publisher-secret volumes. Runtime ntfy cannot read the phone database or app environment; the app never receives the Docker socket.
  • ./webcaller update vX.Y.Z checks an explicit newer release, verifies the bundle/checksums and image references, downloads images before replacing public files, preserves private configuration/volumes, rejects downgrades and checks startup. It does not install unattended updates, automatically archive conversation history or roll back database migrations.
  • Existing source/native installation methods and the README's personal security philosophy remain available.

Verification

144 automated source tests pass. Both native architecture builds run a disposable complete stack: first setup, health/no-store, WebSocket rejection, first identity registration, ntfy access controls and priority-5 delivery, authenticated TURN allocation, private QR generation and persistence after container recreation. Caddy configuration and Cloudflare token-file support are checked. Each test uses a random project name so cleanup cannot affect an installed stack.

Source/history, release archives and publishing output are checked for known private deployment identifiers and credential patterns. The Docker bundle contains only six public installation files; no live environment, database, certificates, private QR, server logs or runtime directory is published. Archive ownership metadata is normalized. Checksums are integrity checks, not an independent signature or security audit.

Before installing or upgrading

This is a preview for a fresh Linux amd64/arm64 installation. Existing deployments are not automatically migrated into new volumes; preserve your current update method and identity database. Updates can interrupt calls. Keep private configuration and any matching backups required by your recovery policy; backups may retain ciphertext past disappearing timers.

DNS, public relay reachability, router/firewall ports and real phone permissions still require configuration/testing. Cloudflare Tunnel alone is not TURN. TURN-TLS certificates/renewal need an explicit operator plan. Physical locked-phone sound, native audio routing and radio handover remain device/network checks.

Olm Double Ratchet, identity pins, SAS and media encryption are unchanged. The Docker alert publisher uses a secret file and an explicitly permitted exact HTTP destination on a private same-host network; external access is HTTPS. iPhone ntfy wake-up still uses the documented upstream metadata relay. This remains an unaudited browser-delivered application, without post-quantum or zero-forensic-trace guarantees. Security model · Verification.