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.
Organic Maps is not at feature parity with paid options but it is pretty damn good for FOSS. I use it almost daily for driving around city/suburban Australia and it very rarely gives me bad directions - certainly no more than the paid option i previously used (Sygic).
It works well, and I’m a huge fan and contributor to Open Street Maps (which it’s bassed on). But it doesn’t do traffic, which is unfortunately wha I need from my navigation apps 99% of the time.
If they had a paid option to cover the costs of using TomTom’s traffic API, I’d make the switch.
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.
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.
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
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.
I agree that it is quite possibly related to the version of Podman moreso than an inherent issue. I am currently satisfied, however, and have no desire to fiddle with it any more… Or at least until Debian 13 gets released.
My use of PinP is almost entirely for cleanliness. It allows me to more easily wipe the build environment (clear out space, troubleshooting). It also mildly improves security as the ‘untrusted’ actions containers run on a separate environment from the important Forgejo container.
The workaround I use for the premade Docker actions not functioning is to simply install Podman as one of the build steps and use that instead, lol. (Some configuration required, but that’s the gist.)
-
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.
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.
You can just write bash scripts in your actions if you want them to be easily replicatable on your local machine, so you don’t really lose anything with that system.
I prefer Gitlab CICD but there are many. Actions had a lot of potential. Then Microsoft bought GitHub and just slapped the Actions label on their CI. If you pull off the mask, it is just Azure devops.
I do too. I kinda miss Jenkins but a lot of the conveniences in GitLab’s CI are really nice and it’s better for 99% of use cases.
Who could have ever anticipated Git hub going to shoot after Microsoft bought it
don’t worry more ai slop in github will fix 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.
is forgejo the same thing as codeberg? it looks similar… just curious
I believe Forgejo lets you self host while Codeberg provides the hosting.
deleted by creator
CodeBerg is a Forgejo instance
Sucks for Organic Maps but that’s the FAANG.
I’m looking forward to the time Forgejo starts supporting Forgefed
Yeah with their recent grant it looks like it’s the next priority, that will be pretty neat:
Downloaded and installed!
👍👍
I’ve switched to CalyxOS 6 or 7 months ago, OrganicMaps came with it. I have never looked back.
I wish, but when I am looking gor a job the employer will look at the green squares and leetcode score or something stupid like that instead of my projects or having a discussion in general.
Very interesting 🤔💭
This is great. Now I can submit issues easier and look into contribution. Storing projects on Github is awful. The signup process is a mess.
