Docker
Run Proxer from the published OCI image.
The OCI image is published to Docker Hub as tinyrack/proxer and to GHCR as ghcr.io/tinyrack-net/proxer.
Check the image version:
docker run --rm tinyrack/proxer --versionRun a Server
Section titled “Run a Server”docker run --rm -p 8080:8080 tinyrack/proxer \ server \ --listen 0.0.0.0:8080 \ --domain proxy.example.com \ --token dev-tokenThe server does not require a volume. Tunnel registrations live in memory and are recreated when clients reconnect.
Docker Compose
Section titled “Docker Compose”services: proxer: image: ghcr.io/tinyrack-net/proxer:latest command: - server - --listen - 0.0.0.0:8080 - --domain - proxy.example.com environment: PROXER_TOKEN: dev-token PROXER_TRUSTED_PROXIES: loopback,private ports: - "8080:8080" healthcheck: test: ["CMD", "proxer", "--version"] interval: 30s timeout: 5s retries: 3Kubernetes Health Probes
Section titled “Kubernetes Health Probes”Use the fixed health endpoints when a platform can probe HTTP paths:
/__proxer__/health/live/__proxer__/health/readyThe control endpoint is also fixed:
/__proxer__/controlEnvironment Variables
Section titled “Environment Variables”The server can be configured with PROXER_ environment variables:
docker run --rm -p 8080:8080 \ -e PROXER_DOMAIN=proxy.example.com \ -e PROXER_TOKEN=dev-token \ -e PROXER_TRUSTED_PROXIES=loopback,private \ ghcr.io/tinyrack-net/proxer serverUse --trusted-proxy flags or PROXER_TRUSTED_PROXIES when the container receives traffic from a reverse proxy you control.