I'm trying to understand the relationship between #cgit and cgit-pink. Do I understand correctly that cgit-pink was forked when cgit stopped development, but has itself since stopped development, and now cgit is active again? (Also trying to figure out whether the "Don't use this!" message on cgit-pink applies to the whole fork or what)
#Microsoft has been passionately ruining everything #GitHub was to many, duct taping #LLM slop anywhere and everywhere. And #GitLab looks at this and thinks... Yeah, let's do that too, that looks awesome?

This is pathetic.

I guess all hope for open source and hopefully slop-free solutions that can help build and maintain communities around code now really truly lie with #Forgejo, #SourceHut, #GameOfTrees, and something like #cgit I suppose? But for how long will that remain true?

Damn.
Would love to tinker around with #mercurial is there a alternative to #cgit which can do #hg?
I wanted to install a remote #fossil web server with multiple projects, but I couldn't figure out some things, like how 😄.

So my #cgit server is back, this time on
https://git.wittamore.fr
cgit

Descubre Beszel: Monitorización ligera para tus contenedores - ochobitshacenunbyte

Descubre Beszel, el monitor de servidores ligero y Open Source ideal para Docker y Raspberry Pi. ¡Controla tu Homelab!

ochobitshacenunbyte

I am blown away again and again by how freakin powerful #nix is.

I am currently setting up a VPS for my private project, with a development mailinglist that is actually a receive-only mailinglist that forwards mails to a public-inbox instance that can be used with `lei` to "subscribe" to.
That host also contains a #git repository with a #cgit web frontend.
It also hosts a website (static site compiled) of the project.

All of that is tested with nixos VM tests. I did not even yet rent that VPS, I am currently configuring and defining the whole thing, I write tests that everything works as expected (sending mail which then appears in the public-inbox frontend, the cgit web interface is reachable, I can push to the underlying repository... and so on).

As soon as things work, I can look for a VPS hoster and then deploy that thing and hit the ground running right there.

Absolutely amazing.

[ANNOUNCE] CGIT v1.3 Released

[ANNOUNCE] CGIT v1.3 Released

It has been heartening to see the steady trickle of projects moving away from Microsoft GitHub to #FOSS friendly code forges like #Codeberg and #SourceHut, or self-hosting with tools like #cgit and #Forgejo

#Gentoo has been up and running on Codeberg all week which has made it easier for me to contribute to the O/S I use every day.

I'm now Proxy Maintainer for a handful of packages, including #VinylCache who also moved their bug tracker on Monday, making it possible for me to contribute 😀

A few years ago, I migrated my personal projects from #GitHub via self‑hosting (#Gitea, #Forgejo) to plain #SSH‑backed bare repositories and a read‑only web frontend (#cgit). What have I really lost?

I've lost much visibility, that's obvious. But I’ve also lost the low‑effort PRs, the hostile forks, and the hard to understand issues. For personal projects, that's a good trade‑off. The most important thing is to be able to link to a project and I still have that thanks to the #frontend.

[1/3]