Containly 2.3.0: backup schedules, S3, SFTP and database dumps

Containly 2.3.0 is out. The backups from 2.2.0 get schedules and targets off the host, and the app tells you clearly when it cannot reach the server.

New with Pro

• Schedules for backup plans: hourly, on chosen weekdays or monthly at a set time. The list shows the next run, and a missed run is caught up on the same day. Without an active Pro licence, scheduled plans pause ("Paused") and resume on their own once Pro is active again; the settings are kept.
• Scheduled verification: a plan reads its newest set back in full every N days (checksums, decryption, manifest).
• S3-compatible targets: Amazon S3, Hetzner Object Storage, Backblaze B2, MinIO, Cloudflare R2, Wasabi and other S3 services, with presets for endpoint and region. Remote targets only accept encrypted sets.
• SFTP targets: password or private key (stored encrypted). The host key is pinned on the first successful connection test and checked on every connection after that.

New and free

• Database dumps for backup and restore: PostgreSQL, MariaDB and MySQL, MongoDB and Redis. Containly detects the databases of a stack by their image and preselects them; the dump runs in the running container without stopping it. Credentials are read from the container at run time and never stored.
• Download and import (.clbk): a complete set can be downloaded as one file and imported on another Containly instance.
• New notification backup.stale: warns when a scheduled plan has had no successful backup for the configured number of days (default 3).
• Manual backups, restore and retention stay free. Sets on Pro targets stay listable, verifiable, downloadable and restorable without Pro; only new writes there need Pro.

No more black screen

• When the app or the installed PWA cannot reach the server, or something in between answers instead (VPN off, reverse proxy or firewall, a proxy sign-in page, a server error), Containly shows the "Containly is not reachable" screen with the likely reason, tips and a retry button. It disappears as soon as Containly answers; unsaved input stays.
• An old tab or PWA after an update reloads once with fresh files instead of staying empty.

Help right from the app

The user menu, the "More" sheet on phones and the new card "Help and community" under Settings, Version link to the guides, this forum and the support chat.

Update

On the Updates page in the app, or in the folder with your docker-compose.yml:

docker compose pull
docker compose up -d

More: Update Containly and Back up and restore data. Questions about the update are best asked in Help and questions.