=> 👽 erick

OMG 💡

I just realized my current approach to generating and hosting my site/blog over HTTPS and Gemini might be flawed. I’ve been generating both sites from a single set of markdown files (which isn’t wrong) using Jekyll, but since my HTTP site is already super minimalistic, why not just use a Gemini proxy to serve the Gemini content over HTTPS instead? 🤯

This is going to be my next mini-project: replacing my regular site with just a proxy. I’m considering Kineto but open to other suggestions!

1 week ago · 👍 m0xee

Actions

=> 👋 Join Station

4 Replies

=> 👽 erick

@mx0xee nice! My setup is pretty similar! I’m also using gmid, but I have Caddy instead of nginx 👍 · 1 week ago

=> 👽 m0xee

That's exactly what I'm doing with m0xEE.Net — it's a Gemini capsule, but when you access it over HTTP(S) nginx calls kineto and throws a nice CSS on top of it. This setup is pretty simple, but gets the job done and it looks nice. In my case gmid which I use to serve Gemini, kineto and nginx are on different machines — but this only makes it a tiny bit more complicated.

Your idea of making links to images display them inline as Lagrange would is good and kineto doesn't look hard to modify that way — I'll look into it, but if you do it first, share the patch! · 1 week ago

=> 👽 erick

@hanzbrix indeed, having markdown in place would make it nicer, but I am really liking the simplicity of Gemini, so I am thinking my site is going to be a Gemini-first site, and the Web version is going to be for the "benefit" of the rest of the world 😉.

That said, I am not planing on completely trashing my previous setup, in case at some point I decide to backtrack. It wouldn't be the first time I do it. · 1 week ago

=> 👽 hanzbrix

It would definitely be easier to deal with than Markdown as the middleman.

Plus you could parse links conditonally, so images could be links on Gemini but auto converted to image/audio/video tags in html. 😁 · 1 week ago