• Neshura@bookwormstory.social
    link
    fedilink
    English
    arrow-up
    5
    ·
    1 year ago

    From my personal experience running GitLab and Forgejo (Gitea Drop-In replacement/Fork):

    • Gitea/Forgejo is easier to get running
    • UI is less bloated/faster
    • GitLab redesigned their UI and imo it’s shit now
    • No features locked behind a “Pro” Version (Pull or Bidirectional mirrors are for example unavailable on GitLab self-hosted unless you shell out for premium)
    • Gitea Actions is a lot more intuitive than GitLab CI, this is likely personal preference but it’s still an important factor
    • haruki@programming.dev
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      Gitlab used to be cute, small, and innovative (as in open). But now it’s too bloated. Gitlab CI is not well designed and half-baked.

    • bionicjoey@lemmy.ca
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      I have no experience with forgejo but I agree with all of the above in terms of gitea v gitlab

    • CubitOom@infosec.pub
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 year ago

      Also, with gitea the table of contents for org files are properly rendered in HTML as it should be. As someone that uses org-mode this is a reason to avoid gitlab.

      But for most people I’d say the less resources that gitea requires means you save on compute and ultimately is cheaper to host.

      I’ve been running my own gitea server on kubernetes and with istio for over 3 years with no issues.