You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 17, 2024. It is now read-only.
We need to set up backups for aosus.
The choice is basically between Duplicati and autorestic.
Autorestic seems nice, and is easy to integrate into our Gitops workflow, but the developer isn't very active cupcakearmy/autorestic#172, and the project lacks a few things.
Duplicati has a simple UI, easy to use, and has all the feature we need, including a smart backup retention method, keeping a copy from every day for a week, then a copy of every week for a month and so on.
However, there are many comments online talking about Duplicati's unreliability, which disastrous in a Backup solution.
It also doesn't support multi-target backups.
And because it's mostly managed in UI, it isn't very gitops friendly, unless we manage it using the CLi.
The text was updated successfully, but these errors were encountered:
We are going to go with Duplicati.
And since we are going to be backing up photos anyway, we might as well use object storage as a CDN.
Discourse CDN using Cloudflare R2 is live, just waiting a couple of days to make sure its stable, then im going to run migrate_to_s3.
We need to set up backups for aosus.
The choice is basically between Duplicati and autorestic.
Autorestic seems nice, and is easy to integrate into our Gitops workflow, but the developer isn't very active cupcakearmy/autorestic#172, and the project lacks a few things.
Duplicati has a simple UI, easy to use, and has all the feature we need, including a smart backup retention method, keeping a copy from every day for a week, then a copy of every week for a month and so on.
However, there are many comments online talking about Duplicati's unreliability, which disastrous in a Backup solution.
It also doesn't support multi-target backups.
And because it's mostly managed in UI, it isn't very gitops friendly, unless we manage it using the CLi.
The text was updated successfully, but these errors were encountered: