← NewTon DC Tournament Manager

Secure by Default

NewTon DC Tournament Manager v5.0.1-beta.7 — March 29, 2026

Download v5.0.1-beta.7

Overview

NewTon DC Tournament Manager v5.0.1-beta.7 adds SSL/HTTPS and mDNS support to the Docker image. Camera features (QR scanning via BarcodeDetector/getUserMedia) require a secure context — HTTPS or localhost. This beta makes it straightforward to run NewTon over HTTPS on a local network without an external reverse proxy.

All changes are in the Docker layer. The application itself is unchanged.


SSL Support

Two supported paths:

When SSL is active, port 2020 redirects to HTTPS (default port 443, configurable via HTTPS_PORT).

The auto-generated certificate includes a Subject Alternative Name covering <hostname>.local, localhost, and 127.0.0.1, so browsers accept it when accessed via the mDNS name without a hostname mismatch warning.


mDNS — newton.local

The container now broadcasts itself on the local network via Avahi (mDNS/Zeroconf). Devices on the same LAN can reach it at newton.local (or a custom hostname) without any DNS configuration.

The hostname is configurable via MDNS_HOSTNAME (default: newton).

network_mode: host is required for mDNS multicast to reach the LAN. This only works on Linux hosts — Docker Desktop for Mac and Windows runs containers in a VM and does not support host networking on the physical LAN. SSL with port mapping works on all platforms.


Docker Compose Files

Two compose files are provided for SSL deployments alongside the existing HTTP-only default:


New Environment Variables

VariableDefaultDescription
SSL_ENABLEDfalseSet to true to auto-generate a self-signed certificate
HTTPS_PORT443HTTPS listening port
MDNS_HOSTNAMEnewtonmDNS hostname → <value>.local

Bug Fixes (Found During Beta Testing)


Files Changed


NewTon DC Tournament Manager v5.0.1-beta.7 — Secure by Default.

Download v5.0.1-beta.7

Previous Releases

For older releases, see the GitHub releases page.