This is from last month, but I haven’t seen any discussion of it. Seems like Forgejo is now a hard fork of Gitea, instead of being a soft fork like it was over the previous year.

The main reason I’m posting it now is this: “As such, if you were considering upgrading to Forgejo, we encourage you to do that sooner rather than later, because as the projects naturally diverge further, doing so will become ever harder. It will not happen overnight, it may not even happen soon, but eventually, Forgejo will stop being a drop-in replacement.”

    • @mholiv@lemmy.world
      link
      fedilink
      English
      701 year ago

      Because gitea is fully the victim of corporate capture. Any PRs that make gitea better in a way that would reduce the main corporate “sponsor” profit are rejected.

      The company has a conflict of interest with the community and it shows. Forgejo is sponsored by a non profit open source cooperative.

        • @mholiv@lemmy.world
          link
          fedilink
          English
          161 year ago

          Right now Forgejo is a drop in replacement. This article is them announcing that Forgejo will eventually not be one.

        • @rjc@lemmy.world
          link
          fedilink
          English
          51 year ago

          If you deployed with docker composr you just change the image and hit redeploy. Super simple.

              • @ikidd@lemmy.world
                link
                fedilink
                English
                11 year ago

                Huh, using their instructions for docker compose, I use docker pull codeberg.org/forgejo/forgejo:7.0.0 and it errors for manifest unknown. Removing the version tag so it default to latest doesn’t help.

                Do I need to make an account and docker login? That seems like it should be unnecessary for a simple pull.

                • chameleonOP
                  link
                  fedilink
                  11 year ago

                  Login isn’t necessary, but there is no :latest tag published so you need to pull a version that exists. The current version is at codeberg.org/forgejo/forgejo:1.21.8-0 or at :1.21 if you want one that tracks patch updates (as found in the container registry).

  • Rose
    link
    fedilink
    English
    21 year ago

    What’s the latest on Forgejo’s Windows builds? Last I checked there was no Windows build due to no volunteers for build/test - Gitea’s old build stuff should still be good.

    Which is a mild shame because Gitea’s Windows version was an insanely simple way to run it if you are a solo dev on Windows and need a private Git site. Drop the binary on an USB hard drive, run it on terminal, boom, done.

    (Currently contemplating just setting up a Raspberry Pi server.)