@AndrzejWasowski I had a similar issue in the past. Moved to #gitolite but found it not feature-rich enough. For simple, single-user repos, it is great.
I wanted more (web UI, PRs, Actions). Therefore I have a mix of #gitolite and #gitea at the moment. But it depends on your intended use-case.

After a shy start of moving the family calendar from #google to #nextcloud last year, this weekend I took the next step: 170 private #bitbucket repos flushed to a self-hosted #gitolite server.

And I am only starting to get the taste of it. It feels very good.

#DigitalSovereignty

#TIL that #Gitolite can't handle repositories with different default branch names. As in, if you push a "main" branch into a "master" server, you get no HEAD 🤦. And you can only change that via SSH-ing to the server and modifying the underlying repository.

Apparently, you could also install a hook to automatically fix HEAD for you: https://groups.google.com/g/gitolite/c/NwZ1-hq9-9E

#Gentoo #git

Set HEAD = first pushed branch

Often times, simplicity is where it is at.

- Don't need a full platform like #forgejo or #gitea (no need for a web interface although both are great projects)

- Don't need need #gitolite to manage users and repos (also great lightweight solution)

- Don't need a new git user on my server as i am the only user

Turns out i had it all along, my main and only user can just instantiate a repo on a empty dir with `git init --bare` and off we go to the races

#git #selfhosting #selfhost #selfhosted

Gitolite is now updated to version 3.6.14 in Guix:

https://codeberg.org/guix/guix/commit/690680eec7b1ffdefa493069f87a1e3ed37271d1

This version makes it possible to use any default branch name for the gitolite-admin repo, not just master. This also means that setting the default-branch field of the gitolite-git-configuration record (to anything other than #f or master) will now result in a working gitolite installation.

#guix #gitolite

gnu: gitolite: Update to 3.6.14. · 690680eec7

* gnu/packages/version-control.scm (gitolite): Update to 3.6.14. Change-Id: I9b0ddc36798d3e5a984ba5bad803d54941066efe Signed-off-by: Andreas Enge <[email protected]>

Codeberg.org
@JosetAEtzel Good luck! Yeah, I’ve tried to avoid closed-source proprietary software and formats whenever possible since - well, free and open source software were a thing. Most of my important stuff is in LaTeX and Markdown. Data is in CSV or, if it needs more structure, SQLite. I’ve recently discovered #Marimo Python notebooks, so I do use those a bit now. Most of the stuff is versioned with #git using self-hosted #gitolite.
@cliffwade #gitolite FTW! If it’s good enough for the kernel folks, it's good enough for me.

@agowa338 If you wanna be a little more fancy, but still very lightweight, #gitolite could be worth considering.

https://gitolite.com/gitolite/

Gitolite

None

@Ric I love to see articles like this. The beauty of distributed version control systems like #git is being able to host on your own machine as well as on open services if you need to collaborate. (I run #gitolite on my #RaspberryPi because I experimented with #gitea and decided I could get by with a more minimalist solution.)
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/
Jeff's Repos