Don’t use the kube stuff. That’s entirely seperate from Quadlets and some sort of Kubernetes compatibility.
Admin on the slrpnk.net Lemmy instance.
He/Him or what ever you feel like.
XMPP: povoq@slrpnk.net
Avatar is an image of a baby octopus.
Don’t use the kube stuff. That’s entirely seperate from Quadlets and some sort of Kubernetes compatibility.
Woodpecker is more mature and I can control access better since I am not the only one using my Forgejo. But I think at some point the built in ones might reach feature parity.
Experimented with selfhosting a Woodpecker CI as a complement to my Forgejo.
Works quite nicely, I just need to set up a native ARM64 agent as the overhead of cross compilation on x86_64 is quite big.
Matrix servers have the problem of highly variable resource use.
Basically if you only use it for some light chatting with friends and family and some niche topic public rooms it isn’t very heavy.
But if any user of your homeserver joins any busy rooms or uses the bridges to join busy public Telegram channels or such, it will quickly outgrow the resources of a reasonably priced VPS.
Personally I would rather recommend you to set up an xmpp server, which can include a gateway to Matrix and other services, but architecturally is much more lightweight and has better mobile clients.
I use one pod per app more or less. The reverse-proxy conf depends a bit on the specific app so that depends, but it will probably work for most by sharing a network and exposing the ports in the pods