401663d55a789d994a981fa3004ba9e6
GIT isn't new to us. I've used Git for over a decade and here in Techrights we've been using it for years, mainly for collaboration. Over a year ago we started self-hosting Git and over time we added more of our codebase/scripts to it. Today we finally publish most of these, however reluctantly (because a lot of it is still crude, the intended userbase being a handful of people at most).
"We emphasise that this is very rudimentary at this point and some tools aren't of much use outside Techrights itself."At the very least, we're hoping to demonstrate a sort of use case for Gemini. I think we might be the first in the world to do such a thing because I spent hours researching what others had done (to avoid duplication of effort). This is just an experimental iteration akin to an alpha release. We emphasise that this is very rudimentary at this point and some tools aren't of much use outside Techrights itself. This can hopefully be changed over time and presentation be significantly improved (remaining bugs ironed out and better/high-quality code that's made generalised).
"Everything starts small and crude. Today is just a start."Gemini has many advantages in this context, including speed, memory footprint, ease of management, and access through any web proxy (better availability). It's hosted from home (Gemini) and our server (Git), with replication set up over Git and a 24-hour (daily cycle) cron job to keep everything updated or synchronised and up to date. We'll probably say more in weeks or months to come. We already have some code that can help convert WordPress blogs and MediaWiki to Gemini, even though it makes certain assumptions about a consistent style and structure.
Everything starts small and crude. Today is just a start. ⬆