act

It's based on act[0] so it's quite like GitHub actions but not completely [1]. I found in the current version of Forgejo the most secure way to set it up was just to put the runner on a different host. There's a Docker in Docker setup [2] that was challenging to get working correctly but still didn't quite feel secure... After setting it all up, I'm convinced GitHub actions as a concept is flawed. I wish the community would make a simpler git-defined CI/CD that didn't have the crazy surface area that actions does... Named shell scripts that can call out to other stuff in the runner Docker image and report it to the UI would be a nice start. [0]: https://github.com/nektos/act [1]: https://forgejo.org/docs/v15.0/user/actions/github-actions/#... [2]: https://forgejo.org/docs/v15.0/admin/actions/docker-access/#...

a bold attempt, how does it compare with https://github.com/nektos/act which has been the de-jure project in this space? Act has never been in my opinion super great, but it's also been several years since I've checked in to revisit the project.

I recently finished building my latest side project and wanted to share it with the world :) It's a CI/CD platform whose whole point is to be more developer friendly and familiar. - YAML is replaced by Python, so you don't need to Google again what is the syntax for ifs or how values are compared in a vendor-specific YAML flavor (e.g. https://docs.github.com/en/actions/reference/workflows-and-a...) - The same engine that runs in the cloud can be run locally and show its output in a terminal UI, so pipelines can be developed and fixed on your laptop without pushing on every change, or needing external tooling that can only get so close to the real thing (e.g. https://github.com/nektos/act) - Because of the above, you can step through your pipeline with any Python debugger to fix it - Artifacts are simply Python values that can be moved aro

You can run your own github actions compatible-ish server. https://github.com/nektos/act Personally my favorite is probably drone-ci. I'd suggest not buying in too hard on any one of these CI systems and just writing shell scripts. Shell scripts are portable, and you can use whatever to trigger them.

There is this : https://github.com/nektos/act

How does this use github syntax? Is it via https://github.com/nektos/act or something similar? I have skimmed through the article but I am unsure of how it is a faster CI. Also perhaps Depot should at this point have their own git provider too (maybe a partnership with gitea/forejo/similar folks?) to become an all in one github alternative too at this point for some customers too :-) I feel like Depot can be interesting for some private repositories github actions

Lowendtalk providers who take 7$ per year deals can provide more reliability than Github at this moment and I am not kidding. If anyone is using Github professionally and pays for github actions or any github product, respectfully, why? You can switch to a VPS provider and self host gitea/forejo in less time than you might think and pay a fraction of a fraction than you might pay now. The point becomes more moot because github is used by developers and devs are so so much more likely to be able to spin up a vps and run forejo and run terminal. I don't quite understand the point. There are ways to run github actions in forejo as well iirc even on locally hosted which uses https://github.com/nektos/act under the hood. People, the time where you spent hundreds of thousands of dollars and expected basic service and no service outage issues is

https://github.com/nektos/act Lets you run your actions locally. I've had significant success with it for fast local feedback.

Would something like this help with the feed back loop? https://github.com/nektos/act

skill issue bro https://github.com/nektos/act

Skill issue bro: https://github.com/nektos/act

do you mean https://github.com/nektos/act or there is something else ?

>Now of course, in some Perfect World, GitHub could have a local runner with all the bells and whistles. Not by GitHub, but isn't act supposed to be that? https://github.com/nektos/act

Would a tool like act help here? (https://github.com/nektos/act) I suppose orchestration that is hiding things from different processor architectures could also very well run differently online than offline, but still.