Organic Maps migrates to Forgejo due to GitHub account blocked by Microsoft.

Comments

• 0x01@lemmy.ml ⁨1⁩ ⁨year⁩ ago

  mastodon.social/@organicmaps/114155428924741370

  Looks like a contributor was in a sanctioned region?

  source

  • Rinox@feddit.it ⁨1⁩ ⁨year⁩ ago

    sanctioned region

    What’s that?

    source

    • zelnix@lemmy.ml ⁨1⁩ ⁨year⁩ ago

      A country the USA doesn’t like

      source

      • -> View More Comments
  • asap@lemmy.world ⁨1⁩ ⁨year⁩ ago

    Looks like a contributor was in a sanctioned region?

    Not according to that thread - it looks like they don’t yet know what caused it:

    mastodon.social/@organicmaps/114178916120483761

    No any details from GitHub yet. One contributor mentioned a temporary visit to disputed areas a long time ago — GitHub probably just flagged the account, and their bots messed up after that.

    source

    • anzo@programming.dev ⁨1⁩ ⁨year⁩ ago

      GAFAM is all one hydra.

      source
• sugar_in_your_tea@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

  Nice!

  I actually recently set up my own Forgejo instance, and it’s remarkably similar to GitHub, to the point where they share Github’s “actions” code.

  Congrats! More hosting diversity is a good thing.

  source

  • Clearwater@lemmy.world ⁨1⁩ ⁨year⁩ ago

    Forgejo Actions is definitely not a turnkey idential-to-GitHub solution, but it’s quite similar and for most not-super-complicated setups it’s basically the same (for better or worse, depending on if you like GH’s Actions).

    As far as I remember, everything that I need works out of the box, except for Docker. In fact, just about everything Docker is somewhat quirky in Forgejo Actions.

    1. One mildly annoying quirk of Forgejo is that as of current, the token generated for each Actions run is not quite the same as GitHub’s token. For my specific use case, if you want to upload a Docker Image to the package repository, you can not use the standard auto-generated token, which GitHub does allow you to use. Forgejo instead currently requires you generate your own app token and use that instead, as the auto-generated one lacks permissions over packages. (codeberg.org/forgejo/forgejo/issues/3571)

    2. Depending on your infrastructure, it might just be impossible to make the various Docker-related actions (such as code.forgejo.org/docker/build-push-action) work. As an example, my infrastructure outlined below is one such case where those actions simply do not work.

    Bare Metal (Debian 12) /
    ├─ Rootless Podman/
       ├─ Forgejo
       ├─ Forgejo Runner
       ├─ Podman-in-Podman (Inner Podman also Rootless)/
          ├─ <Actions Containers Run Here>
    
    * If you use rootful Docker with Docker-in-Docker, those actions will then work as expected. It is just that attempting to make them work with Rootless Podman (at least the version that ships with Debain 12) currently seems to be impossible.
    

    source

    • sugar_in_your_tea@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

      1. that’s really too bad, I hope that gets resolved soon
      2. that’s a pretty old version of podman (4.3 looks like?); also, why have nested podman? My infra is something like this:

      Bare Metal
      ├─ Rootless Podman
         ├─ Forgejo
      ├─ Rootless Forgejo Runner (planning to run on another machine entirely)
         ├─ <Actions Containers Run Here>
      

      I doubt the extra level of nesting is the issue though. If your issue is networking, then maybe the version of podman is the issue, since they switched out the networking layer in 5.0. I upgraded for a related reason, though I’m still getting some odd issues (mostly w/ the DNS resolver).

      I haven’t gotten to cross-compiling just yet, nor have I needed to build a docker image since my projects are very much in the testing phase. But maybe I’ll give it a shot soon, since it’s better to catch these types of issues before it becomes a bigger problem.

      source

      • -> View More Comments
  • neclimdul@lemmy.world ⁨1⁩ ⁨year⁩ ago

    Oh…I was interested until you said actions. What a terrible system for ci.

    source

    • sugar_in_your_tea@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

      What’s wrong w/ actions? Is there something else you prefer?

      I think they’re quite powerful. There are a variety of triggers, runners are fairly easy to configure (easy to scale up), and the syntax is pretty straightforward. It seems to work pretty well.

      source

      • -> View More Comments
  • ernest314@lemm.ee ⁨1⁩ ⁨year⁩ ago

    I love that they have scoped labels while GitHub still doesn’t

    source
  • mesamunefire@lemmy.world ⁨1⁩ ⁨year⁩ ago

    Yep I got one too. Works great and self hosted. I swear its actually faster than GH is nowadays.

    And I like that it doesn’t try to advertise and recommend a ton of repos to do you like GH does now.

    source

    • tdawg@lemmy.world ⁨1⁩ ⁨year⁩ ago

      GitHub has slowly become an advertising platform for repos more than anything. I miss what it was just a couple of years ago. It did exactly what you needed when you needed it. Now it’s just so bloated

      source
    • Zwiebel@feddit.org ⁨1⁩ ⁨year⁩ ago

      The releases page is just as easy to find!

      source