Organic Maps migrates to Forgejo due to GitHub account blocked by Microsoft.
-
is forgejo the same thing as codeberg? it looks similar.. just curious
I believe Forgejo lets you self host while Codeberg provides the hosting.
-
is forgejo the same thing as codeberg? it looks similar.. just curious
Codeberg is an instance of forgejo, yes
-
There is some serious crapitalist hate for organic maps. I never heard of it util is was taken off the play store for a bit. I side loaded it that day.
Well, now I know what will be my daily driver. Thanks!
Anything to reduce the advertising revenue of these jackasses
-
Extremely based
-
-
Wrong thread?
I presume they mean the green squares on their GitHub account.
-
Why did they get removed? I feel like I'm missing a whole backstory here.
-
Continue.
-
Who could have ever anticipated Git hub going to shoot after Microsoft bought it
-
Why did they get removed? I feel like I'm missing a whole backstory here.
They're a direct competitor to one of microsoft's products, and a better one at that.
-
So wait.
GitHub is Microsoft?
I can forgive not knowing github is MS.
but, how in the actual fuck did you not know VS Code is MS?
do you just close your eyes and code blind all day long?
-
Oh...I was interested until you said actions. What a terrible system for ci.
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.
-
Oh come on, it was a really big deal. M$ bought GitHub. FOSS collectively shit itself for a week
-
VS Code has a fully open source base which excludes proprietary extensions and default telemetry ( kind of his AOSP is for Android)
Check here for more info:
https://github.com/microsoft/vscode/wiki/Differences-between-the-repository-and-Visual-Studio-Code
kind of how AOSP is for Android)
https://9to5google.com/2025/03/28/google-android-aosp-changes-announcement/
-
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.
-
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. (https://codeberg.org/forgejo/forgejo/issues/3571)
-
Depending on your infrastructure, it might just be impossible to make the various Docker-related actions (such as https://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.- that's really too bad, I hope that gets resolved soon
- 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.
-
-
kind of how AOSP is for Android)
https://9to5google.com/2025/03/28/google-android-aosp-changes-announcement/
I know
iswas -
And all of them sharing a single 26k connection, too
I heard they got upgraded to DSL
-
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.
Every other ci in existence you just write a command. Then if it doesn't work you run the command on your machine and fix it.
Actions are "magic" which means you have to fake the ci runner with tools and reverse engineer the action to run local debugging and if it failed you might not even fully know what was running with digging into the actions source.
GitHub provides you the tools and their "easy" until they aren't.
It's very Microsoft though. It feels like trying to write a Windows app and trying to get your random
Net environment definition to line everything up and compile in VS then hoping the same thing happens when you deploy.
