Skip to content
  • Hjem
  • Seneste
  • Etiketter
  • Populære
  • Verden
  • Bruger
  • Grupper
Temaer
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Kollaps
FARVEL BIG TECH
  1. Forside
  2. Ikke-kategoriseret
  3. The #gitea developers concluded after 10 years that it is not able to host its own development and that they depend on #GitHub.

The #gitea developers concluded after 10 years that it is not able to host its own development and that they depend on #GitHub.

Planlagt Fastgjort Låst Flyttet Ikke-kategoriseret
giteagithub
18 Indlæg 16 Posters 0 Visninger
  • Ældste til nyeste
  • Nyeste til ældste
  • Most Votes
Svar
  • Svar som emne
Login for at svare
Denne tråd er blevet slettet. Kun brugere med emne behandlings privilegier kan se den.
  • davidak@chaos.socialD davidak@chaos.social

    The #gitea developers concluded after 10 years that it is not able to host its own development and that they depend on #GitHub.

    https://github.com/go-gitea/gitea/issues/1029#issuecomment-4269181192

    At the same time, the community fork @forgejo is self-hosted for a long time and is also powering the popular @Codeberg and at least 8 other public instances. So this seem to be a good time to migrate if you haven't already.

    https://forgejo.org

    blahajj@mastodon.socialB This user is from outside of this forum
    blahajj@mastodon.socialB This user is from outside of this forum
    blahajj@mastodon.social
    wrote sidst redigeret af
    #9

    @davidak lol

    1 Reply Last reply
    0
    • davidak@chaos.socialD davidak@chaos.social

      The #gitea developers concluded after 10 years that it is not able to host its own development and that they depend on #GitHub.

      https://github.com/go-gitea/gitea/issues/1029#issuecomment-4269181192

      At the same time, the community fork @forgejo is self-hosted for a long time and is also powering the popular @Codeberg and at least 8 other public instances. So this seem to be a good time to migrate if you haven't already.

      https://forgejo.org

      moepman@social.troll.academyM This user is from outside of this forum
      moepman@social.troll.academyM This user is from outside of this forum
      moepman@social.troll.academy
      wrote sidst redigeret af
      #10

      @davidak I would swap gitea for @forgejo right now if there was a documented way to migrate that is not ever user has to move every repo on its own.

      mahlzahn@nerdculture.deM 1 Reply Last reply
      0
      • abekonge@venner.networkA abekonge@venner.network shared this topic
      • davidak@chaos.socialD davidak@chaos.social

        The #gitea developers concluded after 10 years that it is not able to host its own development and that they depend on #GitHub.

        https://github.com/go-gitea/gitea/issues/1029#issuecomment-4269181192

        At the same time, the community fork @forgejo is self-hosted for a long time and is also powering the popular @Codeberg and at least 8 other public instances. So this seem to be a good time to migrate if you haven't already.

        https://forgejo.org

        abekonge@venner.networkA This user is from outside of this forum
        abekonge@venner.networkA This user is from outside of this forum
        abekonge@venner.network
        wrote sidst redigeret af
        #11

        @davidak this is ironic

        1 Reply Last reply
        0
        • davidak@chaos.socialD davidak@chaos.social

          The #gitea developers concluded after 10 years that it is not able to host its own development and that they depend on #GitHub.

          https://github.com/go-gitea/gitea/issues/1029#issuecomment-4269181192

          At the same time, the community fork @forgejo is self-hosted for a long time and is also powering the popular @Codeberg and at least 8 other public instances. So this seem to be a good time to migrate if you haven't already.

          https://forgejo.org

          compfu@mograph.socialC This user is from outside of this forum
          compfu@mograph.socialC This user is from outside of this forum
          compfu@mograph.social
          wrote sidst redigeret af
          #12

          @davidak @forgejo We're using gitea at work. I didn't know about forgejo back when I picked it.
          Do you know if there is a way to import gitea's database of issues and pull requests into forgejo?

          (If this is something I can easily look up myself, please let me know.)

          mahlzahn@nerdculture.deM 1 Reply Last reply
          0
          • davidak@chaos.socialD davidak@chaos.social

            The #gitea developers concluded after 10 years that it is not able to host its own development and that they depend on #GitHub.

            https://github.com/go-gitea/gitea/issues/1029#issuecomment-4269181192

            At the same time, the community fork @forgejo is self-hosted for a long time and is also powering the popular @Codeberg and at least 8 other public instances. So this seem to be a good time to migrate if you haven't already.

            https://forgejo.org

            feld@friedcheese.usF This user is from outside of this forum
            feld@friedcheese.usF This user is from outside of this forum
            feld@friedcheese.us
            wrote sidst redigeret af
            #13
            @davidak @forgejo @Codeberg disingenuous. They want some Github-specific features and to not have to deal with hosting infrastructure because they're developers not sysadmins/network engineers.

            meanwhile Codeberg has had several DDoS/AI-crawler related outages. 4 months ago they were only hitting a 90% uptime... so I guess they're comparable to Github in that respect

            but also it's hard to take their hosting infra seriously when they do stupid stuff like make their status page a subdomain of codeberg.org. This is a big nono, you always host your status page on a completely separate domain and ideally on a different Autonomous System
            1 Reply Last reply
            0
            • compfu@mograph.socialC compfu@mograph.social

              @davidak @forgejo We're using gitea at work. I didn't know about forgejo back when I picked it.
              Do you know if there is a way to import gitea's database of issues and pull requests into forgejo?

              (If this is something I can easily look up myself, please let me know.)

              mahlzahn@nerdculture.deM This user is from outside of this forum
              mahlzahn@nerdculture.deM This user is from outside of this forum
              mahlzahn@nerdculture.de
              wrote sidst redigeret af
              #14

              RE: https://floss.social/@forgejo/116441502237665413

              @compfu @davidak @forgejo

              1 Reply Last reply
              0
              • moepman@social.troll.academyM moepman@social.troll.academy

                @davidak I would swap gitea for @forgejo right now if there was a documented way to migrate that is not ever user has to move every repo on its own.

                mahlzahn@nerdculture.deM This user is from outside of this forum
                mahlzahn@nerdculture.deM This user is from outside of this forum
                mahlzahn@nerdculture.de
                wrote sidst redigeret af
                #15

                RE: https://floss.social/@forgejo/116441502237665413

                @MoepMan @davidak @forgejo

                1 Reply Last reply
                0
                • cinebox@masto.hackers.townC cinebox@masto.hackers.town

                  @davidak @forgejo “we can’t use Gitea because no AI. Also our server keeps going down from the AI crawlers” bruh

                  gedankenstuecke@scholar.socialG This user is from outside of this forum
                  gedankenstuecke@scholar.socialG This user is from outside of this forum
                  gedankenstuecke@scholar.social
                  wrote sidst redigeret af
                  #16

                  @cinebox @davidak @forgejo lol, stumbled over that part ass well, don't even seem to see the irony in that!

                  1 Reply Last reply
                  0
                  • feld@friedcheese.usF This user is from outside of this forum
                    feld@friedcheese.usF This user is from outside of this forum
                    feld@friedcheese.us
                    wrote sidst redigeret af
                    #17
                    @mark22k ahh yes thx

                    codeberg.org and codeberg.eu are AS29670

                    status.codeberg.org and status.codeberg.eu are AS24940

                    so they put it on a separate AS which mitigates that problem but not a different domain

                    codeberg.org uses dnsowl.org

                    codeberg.eu uses gandi.net


                    so if DNS for one of those goes down, the status page goes down too...
                    gusted@social.linux.pizzaG 1 Reply Last reply
                    0
                    • feld@friedcheese.usF feld@friedcheese.us
                      @mark22k ahh yes thx

                      codeberg.org and codeberg.eu are AS29670

                      status.codeberg.org and status.codeberg.eu are AS24940

                      so they put it on a separate AS which mitigates that problem but not a different domain

                      codeberg.org uses dnsowl.org

                      codeberg.eu uses gandi.net


                      so if DNS for one of those goes down, the status page goes down too...
                      gusted@social.linux.pizzaG This user is from outside of this forum
                      gusted@social.linux.pizzaG This user is from outside of this forum
                      gusted@social.linux.pizza
                      wrote sidst redigeret af
                      #18

                      @feld@friedcheese.us @mark22k I'll propose internally to setup a mesh network of HAM radio's around the world that can broadcast the status of Codeberg's infrastructure.

                      If DNS goes down of codeberg.org and codeberg.eu, HAM radios are clearly the last reliable resort and there's clearly no bigger issues that Codeberg (or the world) would be facing at that time.

                      1 Reply Last reply
                      0
                      • niels@social.data.coopN niels@social.data.coop shared this topic
                      Svar
                      • Svar som emne
                      Login for at svare
                      • Ældste til nyeste
                      • Nyeste til ældste
                      • Most Votes


                      • Log ind

                      • Har du ikke en konto? Tilmeld

                      • Login or register to search.
                      Powered by NodeBB Contributors
                      Graciously hosted by data.coop
                      • First post
                        Last post
                      0
                      • Hjem
                      • Seneste
                      • Etiketter
                      • Populære
                      • Verden
                      • Bruger
                      • Grupper