Nice reading on how to prevent AI crawlers to hammer #FreeBSD's git repo using #cgit and #nginc https://blog.sysopscafe.com/posts/ai-crawlers-hammering-git-repos/
I don’t expect much has changed since I wrote https://lwn.net/Articles/967922/
For personal independence of development is IMHO better what we have right now working … #SourceHut or #Cgit, #Mailman, #Bugzilla on your own server.
How I setup cgit for a browsable liveslak repository
I received a request to document how I configured the backend for https://git.liveslak.org/ . This is where my git repository for liveslak is accessible and browseable using cgit as the engine.
Of course the server is also running an actual git repository service which people use to clone the liveslak files and f
https://alien.slackbook.org/blog/how-i-setup-cgit-for-a-browsable-liveslak-repository/
Today these beauties arrived ready for the big Beastie upgrade tomorrow. I'll be removing the test boot drive and fitting the 1Tb SSD then installing #FreeBSD . After that I'll install and setup these two 4Tb drives as raid1 and move some of the stuff like /home and other stuff over to them. Then I'll spend the rest of my time setting up the #Bastille jails for #cgit , #Syncthing , #Radicale and possibly #LMS .
#RunBSD #HomeLab
If I plan to move a good amount of my personal projects over to an email patch workflow (instead of PR/issue GUIs) what platform makes the most sense?
I assume sourcehut has more of a "discovery" factor, so my cgit could always remain as a remote backup?
Really debating running my own instance of cgit. No fault of sourcehut, but my repos are so “unpopular” that I don’t need a lot of the bells and whistles offered.
Only issue is integrating patches / TODOs. Maybe just through Git email directly to my personal address?
On the note of #podman, I have not been able to get #forgejo (gitea fork) working, something about permissions, probably an issue with rootless podman. For my use it's a bit overkill anyways and I'm thinking of switching to something simpler. I've heart of #gitolite and #cgit or #gitweb as good alternatives but am open others.
Input and boosts appreciated!
GitHub is nothing more than a search engine for FOSS - it is the new #FreshMeat .org
Or at least, that's all it should be, where it's only used to mirror repos from other self-hosted #git servers.
I'm not deleting my GitHub account - it does have utility and I intend on continuing to engage #FOSS projects hosted there, but anything I really like I mirror or migrate to my own #Gitea servers.
And there's #cgit - maintained by the creator of #Wireguard.
.
I didn't expect cgit to look so beautiful
This week I migrated by git server from gitea to #cgit, and I am loving it. I wrote a small post about my experience @ https://mcol.xyz/2020/08/bye-gitea-hello-cgit.html
Dear #lazyweb, what's the largest #cgit instance you know, in terms of hosted #git repositories?
The standing champion is http://git.savannah.gnu.org/cgit/ , but I'm confident there are larger instances out there…
@kensanata I have three questions on your migration to #cgit from #github. What made you pick it over the other options, including #fossil (which I know is different)?
Are you going to put in an easy place where people can access the repos to clone publicly? I found your method of patching pretty easily (email you diffs) but noted the public access was in a comment (somewhere).
Are you using #debian? I notices cgit didn't have a package for it upstream.