Anyway, my blog can now (hopefully!) be reached via the Gemini protocol!
~~gemini://uvokchee.de/index.html~~
update:
gemini://uvokchee.de/index.gmi or
gemini://uvokchee.de/all.gmi
Anyway, my blog can now (hopefully!) be reached via the Gemini protocol!
~~gemini://uvokchee.de/index.html~~
update:
gemini://uvokchee.de/index.gmi or
gemini://uvokchee.de/all.gmi
Okay, 2nd attempt!
Blog is now with gmi files ^^
gemini://uvokchee.de/all.gmi
and/or
gemini://uvokchee.de/index.gmi
(I don't know which works better for you)
Background:
I completely forgot the jekyll build alone was not enough, and I still had to execute a post-conversion step.
The source code is originally based on
https://github.com/Aarontheissueguy/Html2GeminiPy.git
and adaptet at
https://git.uvok.de/html2gemini/
Also, I fixed my dn42 gemini version as well.
Turns out, if you serve multiple pages via agate webserver, you need one /content/... subdirectory for each subdomain
Since I run my #dn42 nodes on a *different* VPS than where my blog is running now, (and I don't want to copy my blog in two places!) I now employ socat.
Also, since I run dn42 inside a Linux network namespace, I also had to utilize NAT.
It's messy and I hate it.
@uvok Welcome on Gemini! I hope you find it peaceful here!
If I could give you some feedback, I suggest your pages be in the ".gmi" format instead of HTML. Gemini readers are not equipped to parse XML/HTML.
Can't wait to subscribe to your feed once your page is the correct format!
Your all.gmi page could be used as a feed simply by adding the publication date (in YYYY-MM-DD format) at the start of each linkβs description.
For example:
2026-06-07 Server migration time (again)
Indeed. I'd missed the feed.gmi page. π