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.”

    • umbraroze@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      7 months ago

      Heh, your comment actually made me finally go and resolve a problem I’ve had since I got this laptop in 2020. I didn’t have SVM virtualisation acceleration enabled because that made Windows unable to boot somehow. A bit of twiddling after, it finally did! VirtualBox runs! Docker runs!

      …but why would I use Docker for something like this. Might as well blow the dust off of my FreeBSD virtual machine and run Forgejo there!

      • Kogasa@programming.dev
        link
        fedilink
        English
        arrow-up
        2
        ·
        7 months ago

        Docker is lighter and easier to manage than a VM. I run a collection of services as docker compose services inside a NixOS host VM. It’s easy to start, stop, monitor, update etc. even from a different computer (via ssh or docker contexts). It’s great.

        • umbraroze@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          7 months ago

          Yeah, I just tried upgrading my Gitea Windows instance to Forgejo via Docker, and it actually works pretty much as easily as it did before. Fantastic! Might just leave it here instead of shoving it all in the VM - I can always do that later if it’s necessary. Having a full VM does have upsides, but in this particular instance this is definitely good enough.