Looking into possibly replacing my GitLab instance, as I find it bloated and heavy on both hardware and maintenance compared to alternatives.

Currently I’m looking at:

  • GitTea
  • Forgejo, as GitTea turned into a for-profit, otherwise that would be the clear choice
  • OneDev

So I’m wondering what the people on here use, and if they have any other suggestions or opinions?

  • haroldstork@lemm.ee
    link
    fedilink
    English
    arrow-up
    23
    ·
    1 year ago

    Gitea is light and fast so I highly recommend it. If you are worried about it being a for profit company, then use the fork, but if they haven’t done any harm, I’d said give them a shot.

  • thedoginthewok@lemmy.world
    link
    fedilink
    English
    arrow-up
    8
    ·
    1 year ago

    What do you mean by “gitea turned into a for profit”?

    I really like gitea, set it up at my last job and it was easy to work with and used very little resources.

  • kopper [they/them]@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    6
    ·
    1 year ago

    if you have a hard time choosing between Gitea and Forgejo I recommend picking Gitea for now, as they haven’t done anything bad just yet, but if they do Forgejo supports migration from Gitea.

    iirc there isn’t an official way of migrating the other way so if Forgejo fucks up you may end up out of luck

    • freddo@feddit.nuOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Certainly looks interesting, though being able to do code review and a more full-fledged CI/CD solution is a requirement.

    • freddo@feddit.nuOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      CI/CD, multiple users, container registry, and a web UI are requirements, though not much more which is why I find GitLab to be a bit over the top.

      • PupBiru@kbin.social
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        1 year ago

        so i just did a quick search and apparently

        Starting with Gitea 1.19, Gitea Actions are available as a built-in CI/CD solution.

        *edited:

        also they support being a package repo, including container registry

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

      since 1.19 Gitea supports CI/CD action runners that are compatible with github actions. I have one that generates a static site from the data I store in gitea and publishes it to netlify.

  • exu@feditown.com
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    I’m using Gitea. I did try OneDev and it is very nice, but mainly intended for single-team usage as it doesn’t use different namespaces for user projects. It’s also very much its own thing, with its own CI/CD for example. Gitea can integrate with other projects much better, like using Woodpecker for CI/CD or logging in with GitHub/GitLab using Oauth.

    I did follow the drama around Gitea/Forgejo, but for now the Gitea company hasn’t done anything wrong, there’s no feature difference (Forgejo aims to be a soft-fork for the moment) and Forgejo had a bit of drama around the lead developer ~1 month after it was founded.

  • kreateer@programming.dev
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    I assume that by now you’ve made a decision, so if I may I’d like to chip in and ask what’s the benefit of self-hosting a Git instance, like the ones mentioned, over using existing free services like GitHub or Codeberg to host your code? What do you gain by hosting this yourself, apart from privacy and security?

    • freddo@feddit.nuOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      I’d say the main benefit gained is sovereignty and a sense of place. This is not for personal use, but rather for a computer enthusiast association that I’m part of, so having our own git to integrate with the rest of our services makes sense. Throw on branding and link it to our SSO.