# Jellyfin at home, published by the instance (ADR 0032): the Jellyfin sidecar's site,
# with Caddy proxying through a WireGuard tunnel to a Jellyfin on the operator's own
# machine (home-jellyfin/), rather than to one beside the instance. Nothing of the home
# network shows: people reach the instance's server alone. Switched on in .env, in place
# of compose.jellyfin.yaml, never beside it:
#
#   COMPOSE_FILE=compose.yaml:compose.jellyfin-home.yaml
#   JELLYFIN_DOMAIN=jellyfin.halkyon.eu
#
# The tunnel is the host's (wg-quick@wg-jellyfin, with the rules letting Caddy alone
# through it), set up once as root: sidecars/README.md, *Jellyfin at home*.

services:
  caddy:
    environment:
      JELLYFIN_DOMAIN: ${JELLYFIN_DOMAIN:?set JELLYFIN_DOMAIN in deploy/.env}
      # The home end's address in the tunnel (D3).
      JELLYFIN_UPSTREAM: 10.61.96.2:8096
    volumes:
      - ./sidecars/jellyfin.caddy:/etc/caddy/sidecars/jellyfin.caddy:ro

  server:
    # No JELLYFIN_URL (D9): the instance looks at jellyfin. on its own domain and
    # suggests it only while it answers, as the home end is away whenever its machine
    # is. It looks through Caddy on edge, not by the public address back in.
    extra_hosts:
      - ${JELLYFIN_DOMAIN:?set JELLYFIN_DOMAIN in deploy/.env}:172.30.80.2