Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Kubernetes has a hell of a learning curve. Once you get your head around it, it can be great but it is a huge lift to learn. For self hosting I'd lean towards docker-compose rather than kubernetes but kubernetes can be nice once you get past the super steep learning curve.
To answer your questions:
I would strongly recommend looking into deployment using docker-compose over kubernetes until you understand containers inside and out. While Kubernetes can be nice it akso adds another layer of difficulty. I say this as someone who uses kubernetes daily for work, uses off the shelf helm charts, and writes their own helm charts from scratch.
Adding to this (which is a solid recommendation and answer BTW), you can try out
podman kube play <your-file>.yaml(see here) before going full k8s or k3s setup to familiarize yourself with the concepts, without moving too far away from the docker-compose ease of use.Regarding question 1, any distro works, but if your are looking specifically for a lightweight, fast to deploy node host os, I recommend opensuse microOS/leap micro or similarly, fedora coreOS. With both you can drop a combustion/butane/ignition config file in a usb installer partition, so you can quickly integrate fresh installs in your cluster (ssh, network config, user accounts, package installs) see https://opensuse.github.io/fuel-ignition/
As the guy whose comment you added to, thanks for pointing out
podman kube play. I've ever used it before and it looks worth playing with. It's a bit limited in terms of what resources it can create if you're used to k8s, but it definitely looks useful for testing and quickly standing up simple apps.Windows works fantastic with k8s/wsl. Y'all just make up shit 🤣.
If the friend likes windows server specifically, they're in for a ride..
I missed that part 🤣. Yeah I wouldn't touch that shit with an 18ft pole.