To use with Git

  • Max-P@lemmy.max-p.me
    link
    fedilink
    English
    arrow-up
    25
    arrow-down
    1
    ·
    1 year ago

    I mainly just use bare SSH and/or point my web server to my repos as I don’t really need a whole UI for stuff I’m pretty much the only one that will ever use it.

    I feel like it’s a git feature that’s often overlook by those that have only used to GitHub/GitLab/Gitea before. Git was originally designed to just be a folder on a server you have SSH access (read-write) or HTTP(S) access (read-only).

    I’ve used Gogs and Gitea in the past but found it overkill for my needs.

    • zaphod@lemmy.ca
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      1
      ·
      1 year ago

      Exactly what I do. Unless you need fancier collaboration features–issue tracker, UI for handling PRs, etc–a bare repo on the other side of ssh plus something like cgit if you want to make the code available via a browser is perfectly sufficient.

  • oldfart@lemm.ee
    link
    fedilink
    English
    arrow-up
    16
    ·
    1 year ago

    Gitea.

    I used raw SSH for years but occasionally I had to share accesss to a repo with sonebody else, and the whole dance with creating an unix user and giving proper permissions was only fun for the first time.

    • maschmann@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      To make this easiert, you could have used gitolite 🙃 That was my first attempt in 2010 or something and it worked fine.

  • terribleplan@lemmy.nrd.li
    link
    fedilink
    English
    arrow-up
    12
    ·
    1 year ago

    I started on Gitlab, which was a monster to run. I moved to Gitea, until the developers started doing some questionable things. Now I’m on Forgejo (a fork of Gitea).

  • activator90@lemmynsfw.com
    link
    fedilink
    English
    arrow-up
    10
    ·
    edit-2
    1 year ago

    Gitea. Because, I don’t know when Big Brother will decide to snoop or takedown my repositories

    But the biggest dilemma I face is everyone’s on GitHub, not on my little Gitea instance. I think I should use GitHub for my public repositories where I need collaboration. Anyway, that’s a different issue

  • lungdart@lemmy.ca
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    1 year ago

    The only selfhosted github I know about is github enterprise.

    If you just want to host git repos, gitea, and gitlab are good. You don’t need that to host git though, git is peer based and doesn’t require a fancy dashboard to work.

      • fireshell@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        Can automate anything you want, a website or wiki use it to roll out any new changes automatically and others use it to test their software. Connects to Gitea/Forgejo as a third party application and requires that it be granted the appropriate permissions in the Settings -> Applications column.

  • Bristlerock@kbin.social
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    I’ve had gitlab/gitlab-ce running on my NAS for 6+ months and it’s been reliable, mostly as a central repository and off-device backup. It has CI/CD and other capabilities (gitlab/gitlab-runner, etc), but I’ve not implemented them.

  • ancoraunamoka@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    I used many of them and settled for bare repos on an host with ssh access

    • gitea / gogs: too many database corruptions I am getting ptsd just talking about it
    • gitlab: too big, too resource hungry for something so simple. Didn’t use 90% of the stuff that offered
    • gitbucket and onedev: those are very good and are sort of setup and forget because they just work. They have different features set so check them out.

    In the end given that I just have a bunch of users and don’t need many fancy features (we share patches over email and matrix) on our community server we are just using ssh and klaus as a web frontend

  • suprjami@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    https://gitolite.com/

    It’s basic SSH-based git, but also allows you to manage permissions for users and groups based on their SSH keys. You do all configuration by editing a file in the adminstration repo and pushing those changes to the server. I don’t want a web interface or any heavy service running all the time so this suits me perfectly.

  • TheHolm@aussie.zone
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    1 year ago

    You can use gitlab. Big and feature rich. or gitea - small neat and have all important features. With gitea add something like “woodpeaker” for CI

  • z3bra@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I use stagit. It runs whenever I push code to a repo, and then serves everything as static HTML pages.

    It only provides a web interface for git repos though, and for the master branch.