home.social

#cgit — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #cgit, aggregated by home.social.

  1. 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)

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

  3. 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.

  4. Do you guys think it'd be worth it to throw away completely my #Gitea instance in favour of #Cgit? What about just leaving self-hosted Git front-ends as a whole and moving to #Codeberg or #SrHt?

  5. 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.

  6. 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]

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

  8. @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

  9. 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 😄

    etienne.pflieger.bzh/a-ecrit/p

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

  10. "Setting up Anubis to protect cgit from AI crawlers"
    sysrq.in/en/article/cgit-with-

    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

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

  12. 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)

  13. 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!

  14. I've transitioned my public repos off of #bitbucket as a start onto my already existing #cgit / #gitolite systems. The fun stuff is at https://git.rainbow-100.com/
  15. Is every #cgit instance a subject to DoS-like attack by search engines?

  16. 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 😆

  17. @LWN

    I don’t expect much has changed since I wrote 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

  18. How I setup cgit for a browsable liveslak repository

    I received a request to document how I configured the backend for 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

    alien.slackbook.org/blog/how-i

  19. @downey

    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.

    #tallship

    .

  20. #git

    Wanna throw #gitea off my VPS, because it's a program that's constantly running in the background, and I'm far too lazy to manually update it every so ofter.

    #gitolite seems more lean, and I can add #cgit as a frontend?

    But even that is overkill, technically, since I'm single-user, no one else besides me pushes to the repo, so a bare git repo which I push to via ssh would totally suffice...

  21. 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.

  22. 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:​

  23. @ahnlak For a GitHub-like experience, I would recommend like others did.

    In my home infra I am happy with a much more minimal .

    It also might be that itself would be enough without any "repo managers" by using it directly to push over ssh to a remote bare repository. In this case I would also look into adding as a lightweight frontend.

    Happy hacking!

  24. Jen náhodou,nepoužíváte někdo na serveru #gitolite s #cgit ?
    S instalací Gitolite problém nemám,jen nevím jak nastavit Cgit.Chtěl jsem to jen vyzkoušet,Cgit má pěkné webové rozhraní a na to mé učení a sváteční gitování je myslím :gitlab:
    zbytečně složitý.

  25. @downey

    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.

    #tallship

    .

  26. @downey

    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.

    #tallship

    .

  27. @downey

    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.

    #tallship

    .

  28. @downey

    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.

    #tallship

    .

  29. 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 😄

    etienne.pflieger.bzh/a-ecrit/p

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

  30. 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 😄

    etienne.pflieger.bzh/a-ecrit/p

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

  31. @whynothugo Here's a more hands-on one from the #sourcehut folks: 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.

  32. I've transitioned my public repos off of #bitbucket as a start onto my already existing #cgit / #gitolite systems. The fun stuff is at https://git.rainbow-100.com/
  33. I've transitioned my public repos off of #bitbucket as a start onto my already existing #cgit / #gitolite systems. The fun stuff is at https://git.rainbow-100.com/
  34. #git

    Wanna throw #gitea off my VPS, because it's a program that's constantly running in the background, and I'm far too lazy to manually update it every so ofter.

    #gitolite seems more lean, and I can add #cgit as a frontend?

    But even that is overkill, technically, since I'm single-user, no one else besides me pushes to the repo, so a bare git repo which I push to via ssh would totally suffice...

  35. 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.

  36. 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.

  37. 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:​

  38. 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:​

  39. 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:​

  40. 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:​

  41. @ahnlak For a GitHub-like experience, I would recommend #Gitea like others did.

    In my home infra I am happy with a much more minimal #gitolite.

    It also might be that #git itself would be enough without any "repo managers" by using it directly to push over ssh to a remote bare repository. In this case I would also look into adding #cgit as a lightweight frontend.

    Happy hacking!

  42. @ahnlak For a GitHub-like experience, I would recommend #Gitea like others did.

    In my home infra I am happy with a much more minimal #gitolite.

    It also might be that #git itself would be enough without any "repo managers" by using it directly to push over ssh to a remote bare repository. In this case I would also look into adding #cgit as a lightweight frontend.

    Happy hacking!

  43. With #cgit I can set configuration variable `section-from-path`, and it makes all repos grouped under their directories like at git.cepl.eu/cgit/. Unfortunately, I cannot find the equivalent for the plain #Gitweb, so git.cepl.eu/git/ looks convoluted.

    Any idea, how to achieve the same effect with gitweb?