Skip to content

Dockify 1.0.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 07 Nov 14:12
· 18 commits to main since this release
v1.0.0
9af19a8

1.0.0 (2026-11-07)

The first release: one server, safe deploys, tested backups and a locked-down control plane.

Added

  • Install on one fresh Ubuntu 22.04 or 24.04 server with one command. The installer checks the signed release and pulls images by digest.
  • Push to deploy from GitHub, per branch, with live build logs and a step timeline.
  • Zero-downtime deploys for stateless apps, gated on a health check, with automatic rollback.
  • Rollback by image id, with no rebuild.
  • Release commands for migrations, run before traffic moves.
  • Managed Postgres and Redis, plus S3 storage, private by default.
  • Six templates: Gotify, ntfy, Memos, SeaweedFS, Uptime Kuma and Miniflux.
  • Preview deploys per pull request, removed when it closes. Forks build only if you opt in, and never get secrets.
  • Encrypted backups to local disk or your S3-compatible bucket, with scheduled restore tests.
  • Restore from the dashboard, into a new database by default.
  • Alert rules per app for down, crash loops and memory, plus host disk, sent to Discord, Slack, Teams, a signed webhook and more, or by email.
  • Email over your own SMTP server for invites, password resets, security notices, alerts and failed deploys.
  • Disk cleanup that keeps rollback images, and a disk alert at 85% by default.
  • Domains through a Cloudflare tunnel with DNS done for you, or direct mode with Let's Encrypt.
  • Env vars per environment, with history and rollback.
  • Streaming logs, and CPU, memory and disk graphs per app.
  • Import of projects and env vars from Vercel.
  • Teams with Admin and Viewer roles.
  • API tokens with expiry, scopes and a project limit.
  • Signed self-updates that dump the database first and roll back on their own.

Security

  • 2FA, a session list and an audit log. Changing what runs asks for your 2FA code again.
  • Builds and deploys reach Docker only through a gate that allows the calls they need and refuses the rest, including pulls from internal and cloud metadata addresses.
  • One container builder: capabilities dropped, never privileged, no host network, folders or ports.
  • Each secret sealed on its own with AES-256-GCM. The master key never enters the database.
  • Every API route has a declared policy, and a test fails if one is missing.
  • The installer refuses a runtime with known escape bugs and blocks containers from cloud metadata addresses.
Assets 9
Loading