home.social

#gitolite — Public Fediverse posts

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

  1. #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: groups.google.com/g/gitolite/c

    #Gentoo #git

  2. #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: groups.google.com/g/gitolite/c

    #Gentoo #git

  3. #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: groups.google.com/g/gitolite/c

    #Gentoo #git

  4. #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: groups.google.com/g/gitolite/c

    #Gentoo #git

  5. #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: groups.google.com/g/gitolite/c

    #Gentoo #git

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

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

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

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

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

  11. Gitolite is now updated to version 3.6.14 in Guix:

    codeberg.org/guix/guix/commit/

    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 or master) will now result in a working gitolite installation.

  12. Gitolite is now updated to version 3.6.14 in Guix:

    codeberg.org/guix/guix/commit/

    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

  13. Gitolite is now updated to version 3.6.14 in Guix:

    codeberg.org/guix/guix/commit/

    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

  14. Gitolite is now updated to version 3.6.14 in Guix:

    codeberg.org/guix/guix/commit/

    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

  15. Gitolite is now updated to version 3.6.14 in Guix:

    codeberg.org/guix/guix/commit/

    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

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

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

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

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

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

  21. @cliffwade #gitolite FTW! If it’s good enough for the kernel folks, it's good enough for me.

  22. @cliffwade #gitolite FTW! If it’s good enough for the kernel folks, it's good enough for me.

  23. @cliffwade #gitolite FTW! If it’s good enough for the kernel folks, it's good enough for me.

  24. @cliffwade #gitolite FTW! If it’s good enough for the kernel folks, it's good enough for me.

  25. @cliffwade #gitolite FTW! If it’s good enough for the kernel folks, it's good enough for me.

  26. 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/
  27. 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/
  28. 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/
  29. @gedankenstuecke GitHub classroom never worked for me in the first place, so I’m happily showing my students how to self-host with #gitolite.

  30. @gedankenstuecke GitHub classroom never worked for me in the first place, so I’m happily showing my students how to self-host with #gitolite.

  31. @gedankenstuecke GitHub classroom never worked for me in the first place, so I’m happily showing my students how to self-host with #gitolite.

  32. @gedankenstuecke GitHub classroom never worked for me in the first place, so I’m happily showing my students how to self-host with #gitolite.

  33. @gedankenstuecke GitHub classroom never worked for me in the first place, so I’m happily showing my students how to self-host with #gitolite.

  34. @jhx as usual when reading about such setup I can't recommend enough: yadm.io In similar vein I also setup (gitolite.com), which I like, but which is probably an overkill in this case. Thanks for sharing, I always love reading about somebody else's setups! 🙌🏻

  35. @jhx as usual when reading about such setup I can't recommend #yadm enough: yadm.io In similar vein I also setup #gitolite (gitolite.com), which I like, but which is probably an overkill in this case. Thanks for sharing, I always love reading about somebody else's setups! 🙌🏻

  36. @jhx as usual when reading about such setup I can't recommend #yadm enough: yadm.io In similar vein I also setup #gitolite (gitolite.com), which I like, but which is probably an overkill in this case. Thanks for sharing, I always love reading about somebody else's setups! 🙌🏻

  37. @jhx as usual when reading about such setup I can't recommend #yadm enough: yadm.io In similar vein I also setup #gitolite (gitolite.com), which I like, but which is probably an overkill in this case. Thanks for sharing, I always love reading about somebody else's setups! 🙌🏻

  38. @jhx as usual when reading about such setup I can't recommend #yadm enough: yadm.io In similar vein I also setup #gitolite (gitolite.com), which I like, but which is probably an overkill in this case. Thanks for sharing, I always love reading about somebody else's setups! 🙌🏻

  39. #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...

  40. #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...

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

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

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

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

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

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

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

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

  49. I have started moving my private repositories to on a at home. GitHub has its uses but git was built for decentralisation. I have previously experimented with self-hosting but I don't need a web interface or collaboration tools for my private libraries and data – SSH and a terminal suit me just fine.
    gitolite.com/gitolite/index.ht

  50. I have started moving my private #git repositories to #gitolite #selfhosted on a #raspberrypi at home. GitHub has its uses but git was built for decentralisation. I have previously experimented with self-hosting #gitea but I don't need a web interface or collaboration tools for my private libraries and data – SSH and a terminal suit me just fine.
    gitolite.com/gitolite/index.ht