Programming

26022 readers

280 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

UlrikHD@programming.dev

bugsmith@programming.dev

Spyro@programming.dev

Today I got my CI/CD pipeline running for Keyboard Vagabond (piefed.keyboardvagabond.com)

submitted 3 days ago by ragingHungryPanda@piefed.keyboardvagabond.com to c/programming@programming.dev

2 comments fedilink hide all child comments

I'm pretty happy with the progress that I've made in the past few days. I'm hosting Keyboard Vagabond, a collection of Fediverse apps for the traveler/digital nomad niche, on a set of VPS's in a self-hosted kubernetes cluster.

One of the points of the services that I haven't been wild about is that I have my registry/docker image cache exposed to the internet more than I would like because I have to push images to it that are larger than the Cloudflare 100MB limit.

I've been selfhosting Gitea on my home computer and finally got the service running on the cluster and migrated the source code over. I then got ci/cd builds running for each of the services and also upgraded them so that each of them has a DB migration pod that runs before the web and workers. Now they're all consistent in that.

The result now is that I no longer have to push build images and the builds can be faster due to not having to go over the internet/wifi as much. Although I've noticed in a few piefed deployments, the pods didn't actually restart, so I'll take another look at that.

But the next phase is to put the registry behind the cloudflare tunnels and finally remove the last bits of ingress-nginx since everything else is now on istio and the gateway api.

I'm pretty happy with this outcome and it felt nice to see things working.

top 2 comments

sorted by: hot top controversial new old

[–] CombatWombat@feddit.online 2 points 3 days ago (1 children)

Uh-oh, seems like trouble in paradise:

upstream connect error or disconnect/reset before headers. reset reason: connection termination

Hope you get everything up and running again — keyboard vagabond is awesome.

[–] ragingHungryPanda@piefed.keyboardvagabond.com 2 points 3 days ago* (last edited 3 days ago)

a damn, thanks for the heads up

edit: nothing a little deployment restart doesn't fix :)
Check it out! I'm pretty happy with the landing page