matchbox
home-ops
Our great sponsors
matchbox | home-ops | |
---|---|---|
5 | 52 | |
1,209 | 1,723 | |
1.6% | - | |
8.8 | 10.0 | |
6 days ago | 5 days ago | |
Go | Shell | |
Apache License 2.0 | Do What The F*ck You Want To Public License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
matchbox
-
[HELP] PXE Boot without data loss
I also just came across Matchbox.
-
Wanna restructure my server and open for suggestions. What's your tech stack?
Software: * matchbox runs on one RPi for provisioning hardware * The remaining RPis and NUCs all run CoreOS * The matchbox server is responsible for deploying CoreOS to everything * Terraform deploys Kubernetes using Typhoon, 3 x masters (RPis) and 3 x workers (NUCs)
-
The evolution of my homelab over 1.5 years: from a simple Docker Compose file to a PXE-booted, GitOps-managed multi-node Kubernetes cluster
I have no idea why, but it's this, yes? https://matchbox.psdn.io/
- Help picking cobbler replacement
-
We Decided for and Against Ubuntu Core
There have been various different setups here. Have you looked at Matchbox?
> matchbox is a service that matches bare-metal machines to profiles that PXE boot and provision clusters. Machines are matched by labels like MAC or UUID during PXE and profiles specify a kernel/initrd, iPXE config, and Ignition config.
https://github.com/poseidon/matchbox
home-ops
-
Ditching PaaS: Why I Went Back to Self-Hosting
These are great operational wins. Agreed very much that having autonomic (can fix itself) systems at your back is a massive game changer. De-crustifies the act of running things.
The other win is that there's a substantial cultural base to this way to go. Folks have been doing selfhosting for ages, but everyone has their own boutique setup some their way. A couple tools and techniques could be shared, but mostly everyone took blank slate configs & built their own system up, & added their own monitoring & operational scripts.
https://github.com/onedr0p/home-ops is a set of helm scripts and other tools that is widely widely used, and there's a lot more like it. It's a huge build out, using convention and a common platform to enable portable knowledge & sharing.
Self hosting did not have intellectual scale out at it's back, before Kubernetes came along. Docker and ansible and others have been around, but theres never been remotely the success there has been today in empowering users to setup & run complex services.
We really have clawed out of the server-hugging jungle &started building some villages. It's wonderful to see.
-
Homelab setup for Kubernetes training
Going thru this repo https://github.com/onedr0p/home-ops
- Selfhosted k8s for home server?
-
My recently deployed media apps in ArgoCD, migrating from Terraform.
Take a look at my open source GitOps repo managed by Flux here: https://github.com/onedr0p/home-ops
- How do You manage Your docker containers configuration?
-
Self Hosted SaaS Alternatives
Im fully onboard with the geneneral idea as a target.
Right now it's for early early adopters. Hosting stuff is still a painm But we are getting better at hosting stuff, finding stable patterns, paving the path. Hint, it's not doing less, it's not simpler options: it's adopting & making our own industrial scale tooling. https://github.com/onedr0p/home-ops is a great early & still strong demonstration; the up front cost od learning is high, but there's the biggest ecosystem of support you can imagine, and once you recognize the patterns, you can get into flow states, make stuff happen, with extreme leverage far beyond where humanity has ever been. Building the empowered individual is happening, and we're using stable good patterns that will mean the individual isnt so off on their own doing ops- they'll have a lot more accrued human experiene at their back, their running of services isnt as simple to understand from the start but goes much much further, is much more mature & well supported in the long run.
- Deploying apache guacamole on k8s
-
My completely automated Homelab featuring Kubernetes
My Kubernetes cluster, deployments, infrastructure provisioning is all available over here on Github.
-
Container Updating Strategies
For example: https://github.com/onedr0p/home-ops/pull/4528
-
Simple self-hosted S3-compatible
I'm running minio in my cluster with NFS backend just fine. You can see my deployment of it here.
What are some alternatives?
Cobbler - Cobbler is a versatile Linux deployment server
kube-plex - Scalable Plex Media Server on Kubernetes -- dispatch transcode jobs as pods on your cluster!
netboot - Packages and utilities for network booting
cluster-template - A template for deploying a Kubernetes cluster with k3s or Talos
nonguix - Nonguix mirror – pull requests ignored, please use upstream for that
longhorn - Cloud-Native distributed storage built on and for Kubernetes
booty - A simple (i)PXE Server for booting Flatcar-Linux and CoreOS
gocast - GoCast is a tool for controlled BGP route announcements from a host
go-appimage - Go implementation of AppImage tools
motioneye - A web frontend for the motion daemon.
Gource - software version control visualization
renovate-helm-releases - Creates Renovate annotations in Flux2 Helm Releases