view the rest of the comments
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!
Stage 1: Ubuntu server
Stage 2: Ubuntu server + docker
Stage 3: Ansible/OpenTofu/Kubernetes
Stage 4: Proxmox
Kubernetes is overkill for most things not just self hosting. If you need to learn it great otherwise don't waste your time on it. Extremely complicated given what it provides.
fr, unless you're horizontally scaling something or managing hundreds of services what's the point
I agree with this thread, but to answer your question I think the point is to tinker with it j "just because". We're all in this for fun, not profit.
oops straight to stage 4.
but wait stage 3 looks daunting
Don't get me wrong, I use libvrt where it makes sense but why would anyone go to proxmox from a full iac setup?
I do 2 at home, and 3 at work, coming from 4 at both and haven't looked back.
Because it is much simpler to provision a VM
Maybe for the initial setup, but nothing is more repeatable than automation. The more manual steps you have to build your infra, the harder it is to recover/rebuild/update later
You automate the VM deployments.
if you're automating the creation and deployment of vms, and the downstream operating systems, and not doing some sort of HA/failover meme setup... proxmox makes things way more complicated than raw libvirt/qemu/kvm.
Can you please elaborate on this? I am currently using MicroOS and think about NixOS because of quick setup. But also about Proxmox and NixOS on top. Where would libvirt fit in in this scenario?
If you ran a raw Ubuntu/fedora/whatever, you can use qemu/libvrt to run small virtual machines as required. You start and stop them with virsh, define them with simple xml files, and can easily automate the creation/destruction of them if desired.