Eggcellent!! I've improved my #Forgejo workflow and learned how to make it so I can run the workflow without doing a push!
Eggcellent!! I've improved my #Forgejo workflow and learned how to make it so I can run the workflow without doing a push!
A real #forgejoActions workflow! Looks great!
I've made more progress and have a few sample workflows that will help me create one for real.
I'm setting up a #ForgejoActions Runner on my home Linux box so I can run actions for my #Codeberg repos.
I spend more then a week trying to get my small china-box to be accessible from the interwebs.
It was a disaster in as many acts as japanese theater.
No fixed IP to the outside. Anyway ipv-6 only. Most providers STILL cannot handle v6 well. Not to speak about DNS providers.
And in the end the sole purpose why I was doing the whole shit failed, because woodpecker suddenly stopped working right. No reason visible. No up or downgrade was helping.
So its a #forgejoCI runner by now.
Hi @forgejo , I uploaded a small Action for usage with #Forgejo which I created for my own setup running in a local network (on a Raspi!) with a self-signed certificate. The Action trusts a certificate so further operations like the checkout Action or curl work without disabling security checks.
Maybe some else hosting Forgejo in a local network finds this useful. Of course I would be very happy to receive some feedback!
Link:
https://code.forgejo.org/Seltsamsel/trust-self-signed-cert
Wrote a blog post on how to actually *use* the Forgejo Runner to run your unit tests on a clean Docker image. It was a lot harder to make this work than anticipated, and probably did some weird unnecessary stuff, but well. It finally works!
Oh! @forgejo and @gitea have an optional included CI implementation now, and APIs for external CIs to report results back, that's cool!
forgejo.org/2023-02-27-forgejo…
blog.gitea.io/2022/12/feature-…