The catalogue

Backups

Configuration, secrets, databases and projects, encrypted on the server and sent to your own S3 bucket on the interval you set.

Module
core.backup
Category
Base

What it installs

  • Nothing but its settings: the agent itself dumps, archives, encrypts and sends, on the interval you set or when you ask.
  • Each backup in your bucket: the configuration and secrets of the modules, the project list, every database, each project’s folder with its git history, the dev account’s SSH keys and coding-agent sessions, and the extra folders you name.

What it asks you for

  • Nothing about the bucket once the Backups page of the server has it: endpoint, bucket and keys come from there, with the public key backups are encrypted to.
  • The interval in hours — 0 for on demand only — the hour a daily backup starts, and how many scheduled backups to keep.
  • What to include: databases, the dev account’s keys and sessions, projects whole or only their environment files, and extra folders.

Good to know

The server encrypts and cannot decrypt: only your passphrase opens a backup, and nobody keeps it. A part that did not change since the last backup is copied inside the bucket instead of being sent again. Docker volumes are not backed up. See the Backups guide to set up the bucket and to restore.

All services