First, they restricted code search without logging in so I’m using sourcegraph But now, I cant even view discussions or wiki without logging in.

It was a nice run

  • Scrubbles@poptalk.scrubbles.tech
    link
    fedilink
    English
    arrow-up
    85
    arrow-down
    3
    ·
    11 months ago

    Honestly for selfhosters, I can’t recommend enough setting up an instance of Gitea. You’ll be very happy hosting your code and such there, then just replicate it to github or something if you want it on the big platforms.

    • d3Xt3r@lemmy.nz
      link
      fedilink
      arrow-up
      151
      arrow-down
      2
      ·
      11 months ago

      Just so you’re aware, Gitea was taken over by a for-profit company. Which is why it was forked and Forgejo was formed. If you don’t use Github as a matter of principle, then you should switch to Forgejo instead.

          • Scrubbles@poptalk.scrubbles.tech
            link
            fedilink
            English
            arrow-up
            6
            ·
            11 months ago

            It’s more I don’t have them all checked out, and a good chunk are mirrors of github, so I’ll have to list out each one and push to a new remote, mirrors will have to be setup again, and I also use the container and package registries. I’m pretty embedded. It’s not impossible, but it’s a weekend project for sure.

            • zeluko@kbin.social
              link
              fedilink
              arrow-up
              3
              ·
              edit-2
              11 months ago

              If it was just forked, cant you just switch the package/container-image and be done?

                • StarDreamer@lemmy.blahaj.zone
                  link
                  fedilink
                  English
                  arrow-up
                  2
                  ·
                  11 months ago

                  Simply changing the binary worked for me. Been more than 1 month and no migration issues.

                  It does still show gitea branding, however.

                • PowerCore7@lemm.ee
                  link
                  fedilink
                  arrow-up
                  1
                  ·
                  11 months ago

                  If you are using containers, it should be fairly trivial. Otherwise, there might be some renaming to do, but Forgejo should be 100% compatible with Gitea (at least right now). Just make sure you have a good backup in case anything would happen.

        • lambchop@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          11 months ago

          My understanding is the fork isn’t doing much but waiting to see if gitea turns to shit, pushing all their changes upstream. If you use docker I’ve heard you can just pull the new image and it simply drops in, no migration needed.

    • MigratingtoLemmy@lemmy.world
      link
      fedilink
      arrow-up
      26
      arrow-down
      5
      ·
      11 months ago

      Forgejo for you chap.

      Honestly I’m kind of surprised that Gitea is still being recommended on Lemmy, it’s been a while since Gitea was acquired and the community has been raging since. Lemmy is regressing

      • superbirra@lemmy.world
        link
        fedilink
        arrow-up
        14
        ·
        11 months ago

        Lemmy is regressing

        it is not lol, you are just realising that you are not part of any elite for the simple reason of using it

    • SaladevX@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      13
      arrow-down
      8
      ·
      11 months ago

      +1 for Gitea. It’s super lightweight, and works really well! I recently switched to Gitlab simply because I wanted experience with hosting it, but Gitea is much lighter and easier to use.

      • Disregard3145@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        11 months ago

        Its pretty good, for most people there isn’t anything missing

        Actions can’t be triggered by workflow dispatch

        Pull requests can’t wait for status checks