Repository navigation
v1.0.0b3: force HTTPS by default
Pre-release
Pre-release
·
89 commits
to master
since this release
Tabby Sync Version 1.0.0 - Beta 3
HTTPS is now the default. A plain docker compose up -d runs the full stack (Django, Postgres, Caddy) with Caddy as the only published entry point. The backend container has no exposed port and is not reachable from outside the Docker network.
What changed since b2
docker-compose.ymlnow includes the Caddy service, volumes and healthcheck. The backend has noports:mapping. Default image source isghcr.io/mathys-lopinto/tabby-sync:latest.docker-compose.https.ymldeleted. No longer needed.docker-compose.dev.ymladded as an overlay for local development (re-exposes port 9090, disables Caddy).- Gunicorn timeout lowered from 30s to 10s after observing internet scanner noise tying up sync workers on a real deployment.
- README rewritten with a quick start section, updated architecture diagram showing Caddy in the default path, and instructions for importing self-signed certificates into the host trust store.
Deployment
cp .env.example .env
# Fill in DB_PASSWORD, DJANGO_SECRET_KEY, DOMAIN and ACME_EMAIL
docker compose up -d
docker compose exec tabby /app/manage.sh createsuperuserFor LAN/VPN without a public domain, uncomment the tls line in caddy/Caddyfile and run ./scripts/generate-cert.sh before starting.
Image
docker pull ghcr.io/mathys-lopinto/tabby-sync:1.0.0b3