I’ve seen some comments about how “gitlab bad” or whatnot, why do people prefer Codeberg over GitLab?

    • second@feddit.uk
      link
      fedilink
      English
      arrow-up
      17
      arrow-down
      1
      ·
      1 year ago

      That’s a bit of an unfair comparison - that’s the GitLab instructions to install from source. Most people use a package (rpm, deb) to install GitLab.

      The installation instructions for GitLab from prebuilt binaries is https://about.gitlab.com/install/, and that’s significantly shorter.

      That said, I think for most home applications, GitLab is hugely overkill.

      • otl@lemmy.sdf.org
        link
        fedilink
        arrow-up
        8
        ·
        edit-2
        1 year ago

        Yes that’s true. I guess what I wanted to point out is that GitLab has dependencies like Postgres, Redis, Ruby (with Rails), Vue.js… whereas Forgejo can use just SQLite and jQuery.

        • ErwinLottemann@feddit.de
          link
          fedilink
          arrow-up
          12
          arrow-down
          1
          ·
          1 year ago

          sqlite is not something one would use for a database with a lot of users, postresql or mysql/mariadb is a better choice in these circumstances. and i don’t think having jquery as a dependency in 2023 is a positive sign. not sayibg the software is bad, it’s just different.

          • ReversalHatchery@beehaw.org
            link
            fedilink
            arrow-up
            4
            ·
            1 year ago

            Fortunately they were inaccurate, and it supports mariadb and postgre too.
            In the documentation, they leave sqlite and mssql to the last places in the listings.

        • ReversalHatchery@beehaw.org
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          Probably Forgejo/Gitea also uses such dependencies, but their Go counterparts which are statically built into the server binary.

          If resource efficiency only depended on that, Gitlab would be more efficient with memory because of this. We all know that’s not the case, I just said it as a comparison.

          This also means that while Forgejo/Gitea depends less on your system installation, it also wont benefit from updated dependency packages.

        • second@feddit.uk
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          I assume that’s to build from source.

          The times I’ve installed GitLab it’s been a case of dnf install https://.... The rest gets dragged in automatically.

    • andruid@lemmy.ml
      link
      fedilink
      arrow-up
      4
      ·
      1 year ago

      Right. Paid Gitlabs features tend to be targeted as an all in one DevOps platform for larger scale organizations. So how do you do support tickets, CI/CD, feature tracking and coordination for a portfolio of products, documentation, revision control, code reviews, security reviews, etc? In Gitlabs world the answer is Gitlab, with integrations with other enterprise software. It’s HUGE. That said I’ve never heard of an organization (probably due to ignorance not lack of existence) actually doing all of that.

      I personally I’m kind of leaning towards building a proof of concept of forgejo, tekton, and maybe Odoo to see if it can cover what my org is actually doing, but he’ll we pay for tons of stuff but the amount of excell sheets floating around doing this is wild…

      • otl@lemmy.sdf.org
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        Ah come on, we all know as software people we can never stop the spreadsheets from being the real data interchange format ;)

        • andruid@lemmy.ml
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          Hey, at least remote works been really putting nails in the coffin of printed documents floating around.

          But seriously keeping to a good set of tools, providing them at scale and some training will hopefully make the fall back to spreadsheets less attractive to at least the middle wave of adopters.