In my entries for the Weekly Challenge, I use the “bare” language a lot of the time (I’m writing twelve different languages, some of them don’t have package repos, etc.). So my impression of e.g. Ruby or Node.js or Kotlin may be very different from what someone doing the full-fat developer experience might find.
4 Likes
Thinking about using gitea for GitOps. I have an internal GitLab instance and it’s awfully bulky.
Pirmarily looking to do GitOps for DNS (bind9) and proxmox lxc lifecycle management.
My GitLab instance is dog slow. I could move the pgsql in the GitLab virtual appliance to a centralized pgsql container, but I think GitLab will still be a RAM-hog.
Anyone tried GitOps pipeline with both gitea and private GitLab?
I don’t have any pipelines running. Or had. I replaced gitlab with gitea some time ago because gitlab is as you say very bulky and much more exposed than gitea. also migration is often awful with gitlab if you miss a version.
What do you want to use it for? I have gite and I could set up some test when I get home.
1 Like
Currently, I’m not doing any Infrastructure-as-code in my “homelab” (I hesitate to call it that now since my family now relies on portions of it, such as Plex and DNS).
Plex is out of scope for me at the moment for IaC, but I’ve had to fiddle with the DNS portion recently due to hardware failure in my “primary” DNS server.
I have two LXC containers providing DNS service running on my proxmox cluster. One recently corrupted and I had to reinstall it, which made me realize that it is essentially a stock Ubuntu LXC + bind9 package and some files in /etc/bind- which seems to me to be the perfect sort of thing to start with IaC.
I do a bit of IaC at work via Terraform. The community-provided Proxmox TF provider seems fairly robust these days, and I’m contemplating doing LCM on DNS “serving” nodes via GitOps.
While thinking about it, I realized that I’d like to put my BIND9 zonefiles into Git, and as part of that thought process, I discovered an, at least somewhat, established GitOps model for BIND9, where you use pipelines to automatically deploy updated zonefiles to shadow-primary nodes (non-serving BIND9 servers) that then allow zone transfer (AXFR/IXFR). I have shadow-primary and client-seving secondaries already, so I’m interested in exploring that further as well.
I toyed with GitLab runners before, but GitLab is so clumsy already, and the runners add to that even more, I started searching around and saw that Gitea offers automation pipelines in a much more svelte deployment model.
2 Likes
Infrastructure as code sounds like my various docker compose files and my small attempts at using ansible? being a lowly dev, I have no idea really.
what are you doing with DNS in your home network?
I mean sure we are using our zyxel firewall to give IPs to all our devices and I am running a pi-hole as primary DNS for anything that wants to go to the web… … I think mostly that setup works.
I had to google / perplexity proxmox… maybe that will provide me with a solution for running a full Home Assistant alongside my half dozen docker containers on my home server so I can keep the remaining mini server for some other purpose. ha.
I haven’t found time to check out how gitea works with pipelines because I spent hours now fixing the missing not-auto-uploaded images from vacation.
I learned that if you click on “build number” on your pixel phone 7 times (in About Phone) you can summon a djinn enabling developer options on your phone.
3 Likes
Apologies, I meant to come back and flesh out these ideas a bit more.
Unfortunately, jostling my equipment rack recently appears to have precipitated some additional hardware failures- the total loss of the ability to boot my oldest server.
Most of the functions have been migrated to a new server, but I was planning a new project before finishing the rest of it. Oh well, no time for that now, and no money either. Since I did some server updates last year, prices of hardware on the secondary market have more than doubled; the same used Supermicro server I bought last year for less than $300 is now showing up as $800… for the same hardware (which is even 1 year older at this point).
It appears everybody on ebay is buying up old servers, harvesting the RAM to scalp at unreasonable prices, and then trying to resell the RAM-less motherboards for what they paid for them.
Give me a few days to catch up on getting my internet network put back together, and I’ll see if I can show some examples of what I’m talking about
4 Likes