Skip to content
CodeFloe

Backups

Backups are a vital part of a public platform. At CodeFloe, we have backups for the following parts:

  • Database: via pgbackrest. The write-ahead log is archived continuously, with a full backup every Sunday and a diff backup on every other day.
  • Repositories: backed up via restic every hour.
  • Other data: the rest of Forgejo’s data, its search indexes, SSH keys and avatars, the forum, and the service volumes are backed up via restic every day.

All backups are stored in a dedicated object-storage project, in a different region from the live data. See storage for how the two are kept apart.

Because of the IaC approach, no backups of the complete VM or its operating system are needed. Any server can be restored to its current configuration by running an Ansible playbook.