The compose comments, the releases README and the Unraid template told users to list the Docker network's subnet (172.17.0.0/16 on Unraid) in TITANO_TRUSTED_PROXIES. That range holds the gateway, from which Docker relays IPv6 clients and the host's own connections to published ports, and on the default bridge every other container: each could again pick its X-Forwarded-For and X-Forwarded-Proto. The guidance now names the proxy container's fixed address on a shared user-defined network, warns against subnets, the gateway and the default bridge, and sends a proxy on the Docker host to network_mode: host (loopback). The server's parse error no longer suggests a /12 network. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
62 lines
2.8 KiB
YAML
62 lines
2.8 KiB
YAML
# Titano Server with PostgreSQL 17. Start: docker compose up -d Admin panel: http://<host>:8080/admin
|
|
name: titano
|
|
|
|
services:
|
|
titano:
|
|
image: ghcr.io/alby96/titano-server:latest
|
|
restart: unless-stopped
|
|
depends_on:
|
|
postgres:
|
|
condition: service_healthy
|
|
# Publishing a port as another host port ("18443:8443")? Set TITANO_PUBLIC_HTTPS_PORT (and _HTTP_PORT) below to the
|
|
# host port. LAN discovery reaches clients only with "network_mode: host"; on this bridge network clients add the
|
|
# server by its address. With host networking drop "ports", give the postgres service
|
|
# ports: ["127.0.0.1:5432:5432"] and set TITANO_DB_HOST to 127.0.0.1: the name "postgres" no longer resolves there.
|
|
ports:
|
|
- "8080:8080"
|
|
- "8443:8443"
|
|
environment:
|
|
TITANO_ADMIN_USER: admin
|
|
TITANO_ADMIN_PASSWORD: ${TITANO_ADMIN_PASSWORD:?set TITANO_ADMIN_PASSWORD in .env}
|
|
# postgres (with the TITANO_DB_* values below) or a full connection string: Host=…;Database=…;Username=…;Password=…
|
|
TITANO_DB: postgres
|
|
TITANO_DB_HOST: postgres
|
|
TITANO_DB_NAME: titano
|
|
TITANO_DB_USER: titano
|
|
TITANO_DB_PASSWORD: ${TITANO_DB_PASSWORD:?set TITANO_DB_PASSWORD in .env}
|
|
# auto (self-signed), pem or proxy. Behind a proxy, set TITANO_TRUSTED_PROXIES to the proxy's own address (only
|
|
# loopback is trusted otherwise). Give a proxy container a fixed one (ipv4_address, on a network with an ipam
|
|
# subnet that this service joins too) and let it reach Titano on that network, not through a published port.
|
|
# Never list a subnet or the network's gateway (.1): Docker relays connections to the published ports (IPv6
|
|
# clients, the host) from the gateway, and each of them could then choose its client address. For a proxy on the
|
|
# host itself, run this service with network_mode: host; the proxy then reaches Titano over loopback.
|
|
TITANO_TLS_MODE: auto
|
|
# TITANO_TRUSTED_PROXIES: "172.30.0.10"
|
|
# TITANO_PUBLIC_HTTPS_PORT: "8443"
|
|
TITANO_SERVER_NAME: Titano Server
|
|
# Trace, Debug, Information, Warning or Error
|
|
TITANO_LOG_LEVEL: Information
|
|
PUID: ${PUID:-1000}
|
|
PGID: ${PGID:-1000}
|
|
TZ: ${TZ:-UTC}
|
|
volumes:
|
|
# The archive folder should belong to PUID:PGID; an empty or root-owned one is given to them at start (the folder
|
|
# only, never its contents).
|
|
- ${TITANO_ARCHIVE:-./archive}:/archive
|
|
- ${TITANO_DATA:-./data}:/data
|
|
|
|
postgres:
|
|
image: postgres:17
|
|
restart: unless-stopped
|
|
environment:
|
|
POSTGRES_DB: titano
|
|
POSTGRES_USER: titano
|
|
POSTGRES_PASSWORD: ${TITANO_DB_PASSWORD:?set TITANO_DB_PASSWORD in .env}
|
|
volumes:
|
|
- ${TITANO_PGDATA:-./pgdata}:/var/lib/postgresql/data
|
|
healthcheck:
|
|
test: ["CMD-SHELL", "pg_isready -U titano -d titano"]
|
|
interval: 10s
|
|
timeout: 5s
|
|
retries: 10
|