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

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