Hello
As a user, I need something as simple as what is actually implemented and works really great : if something is wrong (hoster fails), I go to aws.amazon.com, download the latest backup, launch a new VM instance, install discourse via docker in a snap and restore the backup.
Probably, but I need a simple restore process. ![]()
In fact, I analyzed the risks (very low) and the cost :
-
Backup process is probably CPU intensive for the VM, but if the system is as smart as “do backup every hour only if something changed”, that will be a good balance to me. “Every hour” could be adapted to each case, for example : “every 3 hours” for a larger instance
-
S3 or alternatives like Hubic are very cheap, and their use will be optimized by the “only if” option
-
Two separate archives (one for the uploaded files, one other for the rest) would definitely optimize the process, but restore should be more tricky.
To be simple and because my instance is very small (60 Mo), I think the only thing I need to start on a cheaper VPS, is to be able to lower the nightly archive frequency to every one or two hours instead of every 24 hours.
Do you know if it is possible to add this hack in the app.yml ?
Many thanks !