#cgit — Public Fediverse posts

Where is the commit log message in the cgit view of this FreeBSD commit?

https://cgit.freebsd.org/ports/commit/?id=06c06ed22442558db4cb0245235418240aa6176b

FreshBSD does show what's required:

https://freshbsd.org/freebsd/ports/commit/06c06ed22442558db4cb0245235418240aa6176b

#cgit #bug #FreeBSD #Git

Where is the commit log message in the cgit view of this FreeBSD commit?

https://cgit.freebsd.org/ports/commit/?id=06c06ed22442558db4cb0245235418240aa6176b

FreshBSD does show what's required:

https://freshbsd.org/freebsd/ports/commit/06c06ed22442558db4cb0245235418240aa6176b

#cgit #bug #FreeBSD #Git

Fixing the cgit configuration of git.slackware.nl

In an earlier article here on the blog, I documented how I have setup cgit to create a browseable web interface to my git repositories, most notably git.liveslak.org and git.slackware.nl. That configuration has worked just fine for years, and you could clone a branch of a repository using the " git URI and that works. However... Cgit is a nice graphical shell around git repositories...

#Slackware #Forgejo #cgit #git

https://blog.slackware.nl/fixing-the-cgit-configuration-of-git-slackware-nl/

Fixing the cgit configuration of git.slackware.nl

In an earlier article here on the blog, I documented how I have setup cgit to create a browseable web interface to my git repositories, most notably git.liveslak.org and git.slackware.nl. That configuration has worked just fine for years, and you could clone a branch of a repository using the " git URI and that works. However... Cgit is a nice graphical shell around git repositories...

#Slackware #Forgejo #cgit #git

https://blog.slackware.nl/fixing-the-cgit-configuration-of-git-slackware-nl/

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)

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)

Would love to tinker around with #mercurial is there a alternative to #cgit which can do #hg?

Would love to tinker around with #mercurial is there a alternative to #cgit which can do #hg?

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.

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.

Check out , fellas

#tool #cgit #webinterface

https://lists.zx2c4.com/pipermail/cgit/2026-February/004968.html

Check out , fellas

#tool #cgit #webinterface

https://lists.zx2c4.com/pipermail/cgit/2026-February/004968.html

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]

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]

While sipping hot Lemon Tea 🍋🫖 and glancing at repos...

#linuxadmin #git #cgit #opensource #tool

While sipping hot Lemon Tea 🍋🫖 and glancing at repos...

#linuxadmin #git #cgit #opensource #tool

@h4ckernews
IMHO its the only true usage of #git 🥳 Any other web hosted vendor lockin monster is only trying to exploit its users.

Hint: There are also tools like #cgit which makes exposing the repo to the web very easy.

Cannot understand people complaining about github politics. Just THROW IT AWAY and host it yourself 🤷‍♂️ Every self-hosted project is a win for true freedom and will help defeat far too mighty monopolys.

Thanks for showing how easy it actually is 👍

#git #github #unplugtrump

My #VServer rental is beginning to take shape.

This weekend I still need to set up #certbot, and then I can change my DNS entries from the current #GitHub Pages address to my #SelfHosting (if you can call it that while running on a rented VServer...) setup.

Next I'm planning to mirror my personal git projects, and to set up #cgit. Once that's up and running, I'll branch off, and put a last commit on all of the repos on Github, that informs about the move.

My #VServer rental is beginning to take shape.

This weekend I still need to set up #certbot, and then I can change my DNS entries from the current #GitHub Pages address to my #SelfHosting (if you can call it that while running on a rented VServer...) setup.

Next I'm planning to mirror my personal git projects, and to set up #cgit. Once that's up and running, I'll branch off, and put a last commit on all of the repos on Github, that informs about the move.

I just published a new #blog article on how to configure #Hiawatha webserver to protect a #cgit instance with #Anubis.

I may be the only one with this setup, but just in case, here are some details on how to achieve it 😄

https://etienne.pflieger.bzh/a-ecrit/protecting-cgit-with-anubis-and-hiawatha.html

(⚠️ answers to this toot will appear on my blog as comment as well)

"Setting up Anubis to protect cgit from AI crawlers"
https://sysrq.in/en/article/cgit-with-anubis.md

This is my new attempt at writing a useful guide! In the article I try to explain my current configuration for running cgit (or any other CGI application) with Anubis.

The guide suggests using uWSGI to serve CGI, with Nginx being a reverse proxy.

#cgit #Anubis #HomeServer #Selfhosted #Selfhosting

A quick round of important places .....show off .... You know, I am good at it 😜🤣

#cgit #linuxadmin #opensourcedevelopment #linux #operatingsystem

My own #cgit instance is flooded by (probably #ia related 🤬) #scrappers, coming from hundreds of various ip ranges, what makes the hosting VM to regularly explodes. Does anyone knows a working method to actually #block those shitbags ? Thank you very much ❤️

(No, robots.txt does not work, I'd like to hear about something else, actually efficient)

My joyful #journey with #openbsd 🐡thickens.
Today I boosted my #selfhosting #services with #nfs, teaming up with #adblock, #caldav, #carddav, #cgit, #httpd, #vnstat, #openntpd

My joyful #journey with #openbsd 🐡thickens.
Today I boosted my #selfhosting #services with #nfs, teaming up with #adblock, #caldav, #carddav, #cgit, #httpd, #vnstat, #openntpd

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/

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/

Getting the grips with #cgit on #openbsd has been so far a great experience.
Fast and simple...
Another one step further into the #selfhost journey at home!

Is every #cgit instance a subject to DoS-like attack by search engines?

Is every #cgit instance a subject to DoS-like attack by search engines?

Found that someone is accessing my git host with a bot ... from a few 100 IPs actually.

Now I have fail2ban added to the setup.

Funnily though, #cgit performs really well and even with a few 100 requests per second, does not bring down my server 😆

Found that someone is accessing my git host with a bot ... from a few 100 IPs actually.

Now I have fail2ban added to the setup.

Funnily though, #cgit performs really well and even with a few 100 requests per second, does not bring down my server 😆

@LWN

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.

#SmallWeb

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/

#Slackware #Software #cgit #git #liveslak

@whynothugo Here's a more hands-on one from the #sourcehut folks: https://git-send-email.io/

After hosting my own #GitHub-style forge for many years (used #forgejo last), most of my private projects are now just plain ssh-hosted repos. Managing the ever growing complexity just stopped being worth it for me. #GitBug and #cgit (simple read-only web frontend) is all I need. Accepting patches/issues via mail only is not ideal, but not dealing with low-effort PRs and lazily filed issues is nice too.

@dvl @freshports Thanks for replying.

Yep, the idea was to append to the URL for the commit to the quarterly branch.

(Retrospective: it took a very long time for me to understand that the branch shown, in cgit, is often not the branch to which a commit relates.)

#cgit #Git

Thank you for the suggestions! In the end, I actually ended up going with #cgit and #gitolite as I felt #gitea and the like are too complex for my use case. I pretty much just need SSH-key based authentication, HTTPS cloning and a nice little frontend, which this combo satisfies.

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! :ablobcatheartsqueeze:​