@ale indeed, there are plenty self-hosted #gitea servers.

This is why #forge federation will be so cool, as it wil tie them together in a large whole, and with that open the ecosystem and create a level playing field, that can weigh up to #Github network effects and #FOMO.

There's also a volunteer collective dedicated to provide easy #hosting of Gitea + #WoodpeckerCI + Pages and the ability to self-host again at any time. And they have a Clinic to help upgrade you self-hosted server: @hostea

@team @humanetech Very interested! I like that k3s is lightweight and easier to understand than k8s from an operator point of view.

At #Hostea the @gitea Ansible playbook is tested end to end to verify @WoodpeckerCI is able to run a job. It is just an example and you can browse the code below.

I'm curious to know what is your strategy for testing your Infrastructure as Code?



Authored by @dachary


@hostea @humanetech @gitea @WoodpeckerCI @dachary at some of our modules we wrote an integrationtest ala

1. spawn a k3d (k3s in docker container)
2. install our app (i think it was c4k-nextcloud)
3. do a backup
4. kill k3d & span another one
5. install app and do a restore
6. make a curl that proves a successful restore.

But I'm not sure that the aspect proven by this test is worth the effort. (1/2)

Sign in to participate in the conversation

Die meissa community.