Docker-compose and a terminal is how I do it. Its simple and effective. I'm able to manage ~20 services that way.
Self Hosted - Self-hosting your services.
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
- No harassment
- crossposts from c/Open Source & c/docker & related may be allowed, depending on context
- Video Promoting is allowed if is within the topic.
- No spamming.
- Stay friendly.
- Follow the lemmy.ml instance rules.
- Tag your post. (Read under)
Important
Beginning of January 1st 2024 this rule WILL be enforced. Posts that are not tagged will be warned and if not fixed within 24h then removed!
- Lemmy doesn't have tags yet, so mark it with [Question], [Help], [Project], [Other], [Promoting] or other you may think is appropriate.
Cross-posting
- [email protected] is allowed!
- [email protected] is allowed!
- [email protected] is allowed!
- [email protected] is allowed if topic has to do with selfhosting.
- [email protected] is allowed!
If you see a rule-breaker please DM the mods!
I use Unraid (an OS). Really liked it for the last few years I've had it.
Docker and portainer. Works good for me as a newbie 😄
I don't even run docker. I just run the Debian packages.
Professionally I am an "Architect" and not much involved in system config (anymore), what I describe below is how I do things for my own, private, servers: Not a big fan of docker, it too often means "cobbled together by a dev not understanding security implications" aka "Institutionalized 'works on my machine'" (of course there are exceptions!). Generally I like using Ansible, because it feels close to how I learned things (ssh, manually), while still making things reproducible (Infrastructure as Code). But, again, not too big a fan of using other peoples "roles", because you never know how well they actually understand what they're doing. I read them for a rough understanding, but usually opt to write my own, based on careful reading of a given software's config manual.
I run a Kubernetes cluster across 3 different servers (nodes) + one small control plane server.
I run vanilla Kubernetes on 4 worker nodes and 3 control planes for high availability.
Unless you're some freak who enjoys K8S so much you don't want to ever get away from it, I don't recommend it
Check out Proxmox hypervisor. Currently running it on an Epyc server I peiced together. Running a dozen or so VMs and a multitude of lxc containers. PfSense routers, docker stacks (I prefer portainer to manage these), Home Assistant, proxy manager, dns server, cloudflare tunnels and game servers, Proxmox easily manages it all. At a cost of $0, its worth checking out.
I also run Proxmox but I added Terraform, Ansible, and Gitea Actions so I can automate the updates and deployment of all my VMs.
I run as much as I can baremetal on Debian. If I can't do baremetal I use podman on Debian.
OMV on one. The other I use Lazydocker. It's excellent
I use unRAID + the docker compose plugin. The main advantage is that hardware updates are super easy:
-
Turn off
-
Replace motherboard and CPU with a completely different one
-
Turn on
(4. If hardware is passed through to a VM, reconfigure the XML)
Done, it just works, so I can just scavenge free hardware from work. Only this year I did AMD>Intel>AMD with very different CPUs and it didn't bat an eye
Proxmox PVE gang. Excellent platform to self-host anything you could want to run from Windows/Linux VMs, LXC containers, Docker, or mix and match. The web GUI makes management easy and gives you a nice dashboard too.