I had a look at the backups today.
Google creates a backup of the PostgreSQL database every day and we keep 30 backups.
In addition Fider offers a pretty powerful mechanism to download all posts, comments, votes, uploaded screenshot ... in a convenient zip. Currently the zip is only 17MB and the content in there is fairly easy to read. I think it's handy to have that as another layer, in case we're not able to restore things on Google (e.g. account is deleted, Google messes up, ...). In such a case, some manual work would be required, but we could even use it to restore the data to a fider competitor.
I now setup a github action that runs every day and downloads the backup.zip into a github actions artifact. Those artifacts are kept for 90 days on github. We could also run the download script somewhere else, but I thought github is a convenient location. Though I'm not sure if we should restrict access to the artifacts more.
@rvanoord @adelinn What do you think?
P.S. Link to a run of the backup
I had a look at the backups today.
Google creates a backup of the PostgreSQL database every day and we keep 30 backups.
In addition Fider offers a pretty powerful mechanism to download all posts, comments, votes, uploaded screenshot ... in a convenient zip. Currently the zip is only 17MB and the content in there is fairly easy to read. I think it's handy to have that as another layer, in case we're not able to restore things on Google (e.g. account is deleted, Google messes up, ...). In such a case, some manual work would be required, but we could even use it to restore the data to a fider competitor.
I now setup a github action that runs every day and downloads the backup.zip into a github actions artifact. Those artifacts are kept for 90 days on github. We could also run the download script somewhere else, but I thought github is a convenient location. Though I'm not sure if we should restrict access to the artifacts more.
@rvanoord @adelinn What do you think?
P.S. Link to a run of the backup