Bon bon, quand on veut : me restait à exécuter un backup distant pour la règle 3-2-1 pour mon #nextcloud , mais je voulais absolument du #arch en #raid 5 avec 4 disques sur un serveur dédié.
4 disques 🆗
arch 🆗
raid : hum, conversion d"un double (/boot + le reste) raid1 to raid5 sur 3 disques pour tester + pérennité de l'action pour monter un S3 (probablement #garagehq ) pour faire du #restic (avec couche #zerobyte par dessus)
time +/- 800min : 🤪
I added an #S3-compatible Storage backend to a #selfhosted #Grist [1] instance. This allows creating forms with "Attachements" in Grist (e.g. users can upload photos). I experimented with several and settled on Zenko Scality #CloudServer [2]:
- #MinIO [3] is somewhat deprecated and not really open source anymore. Its future is unsure.
- #GarageHQ [4] looks pretty great and I wished I could have used this, but it is not yet feature-complete with S3 protocol and specifically missing the versioning feature (I reported this [5])
- #Zenko Scality works out of the box; it is a bit too "big" for my context (aimed at thousands of parallel users) and uses 500MB memory; but it does the job for now.
The S3 Storage protocol is needed in many situations for data infrastructure and allows to decouple persistend data from ephemeral base images (I am considering adding this to my #Mastodon instance, too).
I posted my compose here [6].
[1]: https://github.com/gristlabs/grist-core
[2]: https://github.com/scality/cloudserver
[3]: https://www.min.io/
[4]: https://garagehq.deuxfleurs.fr/
[5]: https://git.deuxfleurs.fr/Deuxfleurs/garage/issues/166
[6]: https://github.com/scality/Zenko/discussions/1779#discussioncomment-15869532
Semur Jengkol
Eric
Adhidarma Hadiwinoto 
Alexander Dunkel
feroxib
Daniel o secours