I tried out Pi-hole many years ago, found it a bit too dumbed down and limited for my taste. I’ve been running Technitium for 5-ish years in my homelab, it’s been rock solid and very pleasant work with. I’ve even deployed it at work for a few projects as well. Been waiting for the clustering feature for a while now, super stoked to see this release.
I’d recommend ZFS for most home server/NAS scenarios. Gives you everything you need, and nothing you don’t.
Stuff like Ceph is just as hungry as it is powerful. The performance sweet spot for Ceph barely begins at 5 dedicated nodes (with at least a dozen drives each, ideally). I could never recommend it for home use unless you want to run it in a lab for the sake of learning.
Source: I’ve designed/built/deployed several 1PB+ Ceph clusters over the last ~5yrs.
Pretty sure you could run Pulp in pull-through mode and add your local Forgejo/whatever registry as a remote, which would at least give you a unified “pull” URL. Then just use Forgejo actions to handle the actual build/publish for your local images whenever you push to main (or tag a release, or whatever).
Pulp might actually be able to handle both on its own, I haven’t ever tried though.
I’d recommend setting your sights on the 3-2-1 rule. 3 copies of your data, 2 different mediums, 1 off-site. Hetzner Storage Box is a good cheap offsite option.
Yeah serverpartdeals is legit. Between work and home, I think I’ve tested & deployed 150+ drives from them over the last 3yrs. No duds, no failures, no complaints. Great customer service on the corp side for big orders, too. 10/10 would recommend.
Move over, bud. That’s my hill to die on, too.
I’d recommend using OpenTofu (Terraform) for initial provisioning of VMs and then use Ansible for post-provisioning config & management. That way you’re letting both tools play to their strengths.
https://registry.terraform.io/providers/bpg/proxmox/latest/docs
Did you mean Netbox?
Well, yeah, thats why I’m saying if the action isn’t available directly from Forgejo, just write out the full action URL like the example in my last comment and pull it directly from GitHub. Most/all of the actions you’re pulling from Forgejo are originally forked from GitHub anyway. ¯\_(ツ)_/¯
With both Gitea and Forgejo, sometimes you need to hardcode the action URL, like:
https://github.com/actions/setup-java@v4
Does docker, pypi, apt, ansible galaxy, etc. I use it at work as part of our undercloud for OpenStack. It’s the go-to for StackHPC, too.
We’re so tightly integrated with the M$ ecosystem at my work, it’s painful. My department has even been going out of it’s way to self host (F)OSS alternatives where we can, just to avoid as much of the cludge as possible.
Has anyone tried out the new Teams integration feature that Mattermost recently rolled out for Enterprise customers? If so, any good?
If we can seamlessly sync calls/meetings from Teams into Mattermost and ditch the Teams client for our day-to-day comms, I might have a fighting chance at convincing my supervisor to pivot my department.
If you ever reach a point where self-hosting does become a possibility, I’d recommend checking out Mattermost.
I used Mailcow for a while before switching to Stalwart out of curiosity. Stalwart was a bit easier to deploy and feels more polished than Mailcow, but they both get the job done.