@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

... Things may be different for a massive hosting facility provisioning thousands of git instances a day ....

Aside of full integration test we have:
1. unittest (c4k is comparable to helm - but every build in convention we can unittest)
2. we build images from (mostly stable base dsitributions) - building fresh easy compared to handling drifted long running servers.

Sign in to participate in the conversation

Die meissa community.