💾 Archived View for rawtext.club › ~sloum › geminilist › 005226.gmi captured on 2023-09-28 at 17:15:30. Gemini links have been rewritten to link to archived content

-=-=-=-=-=-=-

Storing capsule pages?

Kévin lists at gph.dk

Sun Feb 14 02:30:11 GMT 2021

- - - - - - - - - - - - - - - - - - -

12 févr. 2021, 23:46 de d at nnix.com:

Those who have regularly updated pages, though: how do you update them? I've been thinking I'll just use GitHub to store the capsule root, and reference that from the gemini server, but is there a smarter way?

I went full hog, not going to lie here, OH.MG is comprised of four servers and three DreamObjects buckets for data storage, three of the servers are self-hosted on-site in Paris, France and the fourth (for now) is a DreamCompute Instance that pushes updates to the DreamObjects buckets.

I have the production VM at DreamHost, the buckets for Gemini, WWW (+Assets), and Gopher (also at DreamHost), and then the individual servers within my network.

My on-site servers have the DreamObjects buckets mounted as drives (/var/www/html, /var/gopher, and wherever I put my Gemini root), for the moment the cache time is about 5 minutes but I might increase that as you get a lag on the first call if the file hasn't been accessed in a while.

And the prod VM is pretty basic, I use kiln to generate the site contents, then a deploy script that syncs the buckets, and sets the upload to the mirror hosts.

I ramble on a bit here : gemini://oh.mg/project/ <https://oh.mg/project/> or https://oh.mg/project/ <https://oh.mg/project/>

I basically went OTT to see if I could actually make it work and mainly cos I've been burnt a couple of times by self-hosted VMs dying and taking the content with them (and no backups, because YOLO apparently).-Kévin

--Envoi sécurisé avec Tutanota. Obtenez votre propre adresse email chiffrée :https://tutanota.com