Repository navigation
v1.0.0-alpha3: CLI provisioning and ops polish
Pre-release
Pre-release
·
104 commits
to master
since this release
Tabby Sync Version 1.0.0 - Alpha 3
Scripted user provisioning from the command line, a real health endpoint, Docker healthchecks wired up end-to-end, and the last of the upstream dead code gone. No breaking changes.
Highlights
Scripted provisioning
Two new management commands make the user lifecycle fully scriptable:
TOKEN=$(docker compose exec -T tabby /app/manage.sh create_sync_user alice)
TOKEN=$(docker compose exec -T tabby /app/manage.sh refresh_token alice)create_sync_user creates a sync-only user with an unusable password and prints the cleartext token on stdout. refresh_token rotates an existing user's token and prints the new value. Both fail with a non-zero exit code on invalid usernames so shell scripts stop early.
Health and readiness
- New GET /api/health returns plain ok with no authentication, suitable for uptime probes and reverse-proxy checks.
- The tabby service got a Docker healthcheck that pings this endpoint.
- The HTTPS overlay now gates Caddy on service_healthy, so the reverse proxy does not serve traffic until migrations have run and gunicorn is actually answering. No more 502s during boot.
Operational hardening
- JSON-file log rotation on both tabby and db (10 MB per file, 3 files). Long-running deployments no longer fill the disk with container logs.
- Upstream CORS block removed. Tabby desktop is an Electron client, so CORS headers never applied in the first place. django-cors-headers is dropped from the dependency tree.
- Secure cookies are now controlled by an explicit SECURE_COOKIES=True env var, replacing the earlier "inferred from FRONTEND_URL" logic.
Meta
- SECURITY.md documents the private reporting channel.
- README covers /api/health and the new CLI commands.
Upgrade notes
- No migrations added. Existing users, tokens and configs are unchanged.
- .env cleanup: FRONTEND_URL, CORS_EXTRA_URL and BACKEND_URL are no longer read. Set SECURE_COOKIES=True in production deployments behind HTTPS.
- django-cors-headers is no longer installed; if you had a fork that depended on it, reinstall it locally.
Verified
- pytest: 169 tests, 100% line coverage on tabby/.
- End-to-end tests cover the CLI commands against the real API.
- docker compose up -d goes healthy within the start grace period.
Known limitations
- Still alpha. No real deployment exercised beyond the author's machine.