docker-compose.yml

services:
  viofosync:
    image: robxyz/viofosync
    container_name: viofosync
    restart: unless-stopped

    ports:
      - "8080:8080"

    # Optional: pass through the GPU for hardware-accelerated decode/encode
    # (exports). On an Intel iGPU this now uses QuickSync (QSV) first and
    # falls back to VA-API, then software. Uncomment on a NAS with an Intel
    # iGPU. Verify it engaged with:  docker exec <c> vainfo   and check the
    # startup log line "export encoder available: … qsv …".
    # devices:
    #   - /dev/dri:/dev/dri
    #
    # The entrypoint auto-detects the render node's group and adds the app
    # user to it, so this is usually all you need. Some hosts (notably
    # Synology DSM) still require the render group to be granted explicitly —
    # if hardware accel doesn't engage, find the GID with
    #   docker exec <c> sh -c 'stat -c %g /dev/dri/renderD128'
    # and add it here (937 is common on Synology):
    # group_add:
    #   - "937"   # GID owning /dev/dri/renderD128 — the iGPU render node

    volumes:
      # Config directory. A template viofosync.env is seeded here on first
      # run — edit it (ADDRESS, WEB_PASSWORD, etc.) and restart to apply.
      - /path/to/config:/config
      # Recordings (dashcam archive). The state DB lives in /config, not here.
      - /path/to/recordings:/recordings:rw

    environment:
      # UID/GID that owns the host-side config and recordings folders.
      # Run `id <your-user>` to find the right values.
      PUID: 1000
      PGID: 1000

      # Timezone for log timestamps and journey grouping.
      # https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
      TZ: Europe/London