• russjr08@piefed.zip
    link
    fedilink
    English
    arrow-up
    17
    ·
    2 days ago

    Depending on what your needs and available resources are, GitLab is fairly heavy especially in comparison to Forgejo.

    • Kairos@lemmy.today
      link
      fedilink
      English
      arrow-up
      18
      ·
      2 days ago

      Forgejo is also infinitely easier to run. Its a static go binary that uses an sqlite database.

    • KickMeElmo@sopuli.xyz
      link
      fedilink
      English
      arrow-up
      4
      ·
      2 days ago

      Fair! Mind you, the question was genuine curiosity. I don’t have projects of my own hosted at this time, but I may soon.

      • russjr08@piefed.zip
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 days ago

        No worries at all! I battled with that choice for a while when I was self hosting. I had already been so deep into using GitLab CI that it would’ve been a pain to migrate to Forgejo Actions, though to be fair when I had setup GitLab the Actions system didn’t actually exist yet.

        And if you plan to expose it to the Internet, GitLab being a much larger project has more potential security issues to keep up with which is another important note.

        (Though as always when publicly exposing services to the Internet, keep up with patches either way and stay safe!)