💾 Archived View for jean.ribes.ovh › gemini-backend captured on 2022-06-03 at 22:46:07. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2022-04-28)

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

First and foremost, this blog is also available over Gemini [1], gemini://jean.ribes.ovh

What is Gemini ?

Gemini is a protocol which strives to replace parts of the Web (HTTP, that you're currently using). Essentially, it's a stripped-down version of the modern web, without interactive or colorful pages. But also without tracking and (lots of) security holes.

Gemini is limited to text-only content, and isn't interoperable with HTTP. Well, you can't have everything.

[1] Gemini

Some people argue that Gemini was made for the sake of creating an incompatible protocol from scratch, and that it doesn't even address all problems of the web (TLS fingerprinting). One criticism it that you can recreate the Gemini experience by having a simple website without images, javascript ...

I'm not here to decide whether or not Gemini is actually a good idea, but I want to provide content to both Gemini and the HTTP web.

The software

GitHub - JeanRibes/gemini-ghost: serve a Ghost blog content through the Gemini protocol

serve a Ghost blog content through the Gemini protocol - GitHub - JeanRibes/gemini-ghost: serve a Ghost blog content through the Gemini protocol

[‡ fluidicon] [2] GitHub JeanRibes

[‡ gemini ghost] [3]

[4]

The first version fetched the content directly from the SQLite database of a Ghost installation. The issue is that the first database access would lock up Ghost...

So instead I used the Content API, which has the benefit of decoupling the gemini server from the ghost server, and is more resilient against any database schema changes, and also works with MySQL installations.

[2] [‡ fluidicon]

[3] [‡ gemini ghost]

[4]

How it works

On startup, the server fetches all the posts from Ghost, and converts the HTML into Gemtext. The output is cached in RAM for better performances. Every hour, the server fetches all the posts again, in order to reflect any update.

Additionally, there is a webhook endpoint that you can connect to the Site Rebuild Ghost Webhook (which will trigger on any change), or you can also connect it to multiple webhooks (post created, updated ...) for more granularity.

The homepage provides a feed of all the posts, with the excerpt and date. You can customize this page with a Go template (index.tpl). It fetches the blog title, description and navigation and integrates it into the homepage.

Search

The search feature is availably over Gemini and HTTP. It uses the awesome Bleve [5] search library, which provides full-text search.

There is a HTTP API, with CORS headers matching the Ghost content API domain, so you can call it from the Ghost frontend.

[5] Bleve