automatic periodic backups of all data, non-source code

[slivingston]

• the CloudSQL database that is used by the curator-portal
• the users list of artist-portal, as stored in Firebase
• the users list of curator-portal, as stored in Firebase
• the projects JSON-oriented database, as stored in Firebase
• the artworks and albums from artist-portal, the JSON-oriented database, as stored in Firebase.

Note that this is an infrastructural issue that is relevant to other code repositories and resources of Tekuma. However, the list above attempts to limit the scope and admit a clear definition of done.

• For the JSON-oriented databases, consider capabilities that Firebase offers.

[slivingston]

include among the backups copies that are not in Gcloud, preferably to which we have local physical access.

[slivingston]

e.g., the redundancy requirement should be sufficient to allow bootstrapping into a working website again without access to Firebase, GCloud, and AWS.

[xstephen95x]

create a document backups.md in the documentation repo, and log the audit of all backups there.