New Post: Forgejo Workflow Action to Publish a Hugo Blog
https://janusworx.com/work/forgejo-workflow-action-to-publish-hugo-blog/
New Post: Forgejo Workflow Action to Publish a Hugo Blog
https://janusworx.com/work/forgejo-workflow-action-to-publish-hugo-blog/
My #selfhosting progress for the last few months so far #elk
#forgejo
#gotosocial
#invidious
keycloak
mailcow
navidrome
#nextcloud
onlyoffice
openproject
outline
podsync
redlib
rsshub
#searxng
synapse
thelounge
#wireguard
...and I'm not going to stop :)
#selfhosted #selfhost
It's official! Me, @Beowulf, @famfo and @Thelie will carry out a Forgejo Contribution Workshop during GPN23 in Karlsruhe.
Friday, June 20th 2025
ZKM, Karlsruhe, Germany
Gulaschprogrammiernacht '23 (https://gulas.ch)
12:00 - 13:00 CEST
Happy to answer any questions. :)
Getting Forgejo Helm Deployment to Also Trust a Local Certificate Authority
Earlier this week I blogged about getting a Forgejo Action Runner to trust my local Certificate Authority so it could check out projects.Last night while trying to setup Keycloak as a authentication source, I ran into another instance of this problem, this time with the core Forgejo application.
The problem was basically the same, the Keycloak instance is protected by a HTTPS certificate […]
I've been managing my Docker Compose files, that run on a few Raspberry Pis, using a custom Ansible playbook. That all started before I had my local Forgejo instance running.
Now I decided I want to do GitOps to manage the compose files, so I need to decide whether I want to shoehorn it with Portainer, or go full-on Kubernetes (k3s). Time for some testing!
Any #forgejo users managed to mount an extra CA cert with a helm install?
https://code.forgejo.org/forgejo-helm/forgejo-helm/issues/1269
@jednorozec talking about the future of dist-git: AI generated graphics based on current documentation: on the left what dist-git looks like currently (complicated and heavy), on the right what it will look like on #forgejo ! #flocktofedora
Looks like I found three things that my Raspberry Pi 4 are struggling with: building stuff on my Forgejo builder, building ESPHome firmware, and running Ollama for Home Assistant Voice.
I'm not trying to throw shade on Raspberry Pis, not at all. Love them. But it seems like I need something more powerful for those corner cases that I've been finding.
Maybe a Pi 5?
If anyone is interested in contributing to FOSS projects (as everyone here as a lot of free time, right?)
it would be really cool to adjust this change https://review.opendev.org/c/zuul/zuul/+/859939 to support #Forgejo and to land it in #ZuulCI
@LUG_Reutlingen @tuebix Cool, dann treffen wir uns dort vielleicht
Wir erzählen dort über Fortschritte im #Föderierten #Forgejo
https://www.tuebix.org/2025/programm/121-community-in-der-eigenen-hand-fderiertes-forgejo/
OK #ForgeJo folks. My instance is running with HTTPS with a certificate from a private CA. I've stood up the Action Runner in a docker container on a different machine, I mounted the CA cert, but also generated a config file to have it ignore the warning about the certificate when registering, but if I include a step like checkout it fails to pull the repo via the HTTPS URL because the cert is not trusted in the container it runs the action in.
Any suggestions?
/cc @jwildeboer and @jpmens
I've revamped the mobile commit list view in #forgejo recently for use in #Codefloe.
Changes are summarized in https://codeberg.org/forgejo/forgejo/issues/8043.
If you view https://codefloe.com/codefloe/forgejo-codefloe/commits/branch/main on a mobile device (or use the mobile view in your browsers devtools), you'll see the difference to other Forgejo instances (e.g #codeberg).
Not sure if it will ever make it upstream, but I needed this fix so badly, and I couldn't wait for a lengthy (and likely complicated) upstream discussion first ️