#goharbor — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #goharbor, aggregated by home.social.
-
I'd like to introduce #GoHarbor in my #homelab but the setup is so terribly convoluted that it's putting me off.
Why does it need to ship syslog, database and proxy stuff? I don't consider this the responsibility of this software.
Worst of all, it's such a mess that it tries to fix it by providing an installer. Which hides the intentions and makes it even harder to understand how these components relate and how to instrument them.
Might go for Nexus or something else instead.
-
@fyw321 @geerlingguy My 8 node cluster costs around 55W via POE. It is 3 pi4 8G control+worker nodes, and 5 pi4 4G worker-only nodes (1 is actually 8G.)
Storage is #iscsi on spinning rust on #TrueNAS, but you can do all this on local disks.
It handles a LOT:
- #Promstack, #FluxCD, #Calico, various scrapers
- #Adguard
- #Blocky (another adblocking #dns)
- #Jellyfin
- #Ombi, Prowlarr, *arr, Deluge
- Home automation helpers (#ser2sock instances, #zigbee/#zwave 2mqtt, but not HA itself)
- #Argo for builds (deprecated in favor of the x64 cloud lab. Building x64 docker containers on arm is BAD)
- Democratic CSI for iscsi/nfs
- #GoHarbor container registry & #dockerhub cache
- #Mealie recipe manager
- #Monica contact manager
- #SMTP relay to gmail
- #Ubiquiti console (bootstrapping becomes a chicken and egg problem though, if it goes down wrong)
- #Wireguard #VPN server
- #Whoogle
- #VisualStudioCode and a #dind sidecar
- SSL termination for most of the rest of the network