• rowdyrockets@lemm.ee
    link
    fedilink
    arrow-up
    10
    ·
    1 year ago

    As a casual self hoster with Gitea running exclusively to clone GitHub repos for archival purposes. Think Nintendo gaming adjacent and risking DMCA. Is there any reason for me to switch to forgejo while I have the chance?

    • pe1uca@lemmy.pe1uca.dev
      link
      fedilink
      arrow-up
      10
      ·
      1 year ago

      My question would be, if you’re only archiving repos, why do you need a forge?
      A simple git clone <repo> to any your archival directory would be enough to store them, there’s no need for you to use a forge software.

      Are there any other features of gitea you use?

      • rowdyrockets@lemm.ee
        link
        fedilink
        arrow-up
        9
        ·
        1 year ago

        I like having the codebase in an easily presentable way. Git clone with a cron job would work fine but doesn’t tickle my fancy enough.

        • dnzm@feddit.nl
          link
          fedilink
          arrow-up
          6
          ·
          1 year ago

          If you mean a (read-only) web interface, there’s also cgit and gitweb.

          I mean, it’s your party and if Gitea works for you, that’s great. It still is a bigger piece of software than what you need (or at least what you’ve told so far), it’s up to you to determine if you’re fine with that.

    • traceur204@lemmy.blahaj.zone
      link
      fedilink
      arrow-up
      5
      ·
      1 year ago

      As I understand it, forgejo came about when someone maneuvered to consolidate control of gitea. So I guess if you stay you may eventually become subject to various anti-user practices that non-open software tend to gravitate toward