ssh, git and docker compose files.
this post was submitted on 28 Mar 2026
57 points (96.7% liked)
Selfhosted
58187 readers
348 users here now
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: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
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!
founded 2 years ago
MODERATORS
Same, just replace docker compose with cloud-init. Gitea runners for deployment.
Unpopular answer, but Unraid; as i have mixed sized drives.
Proxmox to manage my VMs, SSH for anything on the command line and portainer for managing my docker containers.
One day I will switch probably switch to dockge so my docker-compose files are stored plain on the hard drive but for now portainer works flawlessly.
dockge needs me to maintain my dockercompose on its own folder in /opt/ as root.
I just wanna keep my compare in its own repos
Huh, that's not my case at all, I run everything from the home folder with my user
Yeah, that would be the ideal scenario I guess.
It should technically be possible by mapping the compose files into the opt folder via docker mounts but I think that's an unreasonable way to go about this since every compose file would need a mounting point
I had started out with CasaOS and ran it for a year or so. Last week, I took some time to move everything out of Casa's file structure and cleaned up the compose files.
For container management, I'm using Dockhand. It's been great.
Otherwise, like most others have said, SSH when I need to do more.
Terraform, ansible and kubernetes (microk8s).
K8s in particular has been a huge change to simplifying my network despite the complexities involved and the initial learning curve. Deploying and updating services is much easier now.
Bash? (and Ansible)
Proxmox gui and ssh for my LXCs
...and nix config and podman in the lxc for me
Does proxmox count? Then I run lots of docker containers in lxcs
Virtualmin and cockpit
Home server for me is mostly Ansible for provisioning and systemd for everything else. The trick is keeping it simple enough that you can recover from a broken state without Google. For daily tasks I reach for bare metal SSH or a web interface if it needs to be friendly. K8s is great but I found myself overcomplicating things until I stepped back and remembered: I already know how to SSH into a box.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| Git | Popular version control system, primarily for code |
| LXC | Linux Containers |
| NAS | Network-Attached Storage |
| SSH | Secure Shell for remote terminal access |
| k8s | Kubernetes container management package |
5 acronyms in this thread; the most compressed thread commented on today has 9 acronyms.
[Thread #198 for this comm, first seen 29th Mar 2026, 13:00] [FAQ] [Full list] [Contact] [Source code]
ssh
Power button
ssh
🤔 yeah, that and I guess docker?
SSH and Ansible using SSH
Ansible using SSH
The moment you discover anything else, you're gonna be so pleased. It'll seem so modern! So fast!
Hey, you're the "Ansible is toxic" guy.
What do you use?
So what's your preferred solution and why?
The cli.
I have used management interfaces like coxkpit in the last but i do not really like it that much. I have E-Mail Notifications setup for updates via aptitude and monitor using prometheus and grafana and get additional notifications via prometheus alarm manager.
For an easy to use docker interface i use dockge, since i found it in this use case to be faster with a good, working, independend Interface.
But for the Linux underneath, for all 10-20 servers i managae, CLI.
Cockpit is nice for that. The Podman integration of it is also useful.
+1 to cockpit. My entire network is domain managed and cockpit makes managing everything so much easier
Ansible or ssh
Exactly this! Oh, and gatus for the nice view (mostly own php talking to gatus api)
NixOS and SSH I guess?
- Proxmox GUI for restarting hosts or vms
- Komodo for restarting containers
- Forgejo for configuring and updating containers (deployed by komodo)
- Ansible for OS updates
- Prometheus + Grafana for monitoring
Those for basic stuff, ssh for everything else.
I guess, K3s & argocd? Not sure exactly what you're asking
I run k3s and use Argo CD at work, but it always seemed overkill for my home server. I also would want to use self-hosted Forgejo instead of an external service, but I don’t care to spend time on a setup that bootstraps Forgejo, PostgreSQL and Argo CD, then has all of the above managed by Argo CD.
Forgejo, I can't help ya with that one
Even though me and another guy set up Argo at work, I wasn't gonna do it all over again - I pretty much just copied our manifests from work, swapped out the secrets and github urls, and was on the path to success. And the benefits cannot be understated
load more comments
(2 replies)
ssh and portainer.
Opentofu for all the looking after the config on my proxmox boxes and networking gear. Ansible for everything else.
I don't currently have any monitoring set up but it's in the to do list when I feel like it.
load more comments
(2 replies)
- Portainer for Docker containers
- ssh for most real administration tasks
- Olive Tin for repetitive tasks like sudo apt update
- Netdata for server metrics and ntopng for metrics on standalone pFsense box
So many things. Mostly Kubernetes and FluxCD, but also doco-cd for managing a few deployments on my NAS with GitOps.
My setup is a barebones Alpine Linux with ssh and docker, and everything I run on it is a container (except backups).
Those I manage remotely (remote Docker context), so the only time I have to log in is to do an update for the few system packages and that's it. And for that ssh is more than enough
I'm currently in the process of setting up my home server again but this was basically my setup before. Alpine Linux + SSH + Docker and I kept everything to a minimum.
This time I'm setting up rootless Podman in place of Docker and as of today the switch over is complete.
I'm thinking of trying to use wireguard as a way to secure my ssh port but I'm still trying to learn and figure out if that's possible.
With all the security and trust issues hitting the self-hosting headlines, less and simple is completely fine with me.
For system and docker stats I can only recommend beszel. Portainer for docker management and anything else ssh.
I second Beszel, it's such a clean interface, and I can also have it send alerts through Gotify if my shit breaks!
Ssh, dockhand, beszel. They have nice GUI and setting up notification providers is easy. I am using ntfy, so if my CPU is peaking at 90% for a while, or I if any of the containers become unhealthy I get notification to my phone.
load more comments
(1 replies)
I’m running OMV with the Docker Compose plugin and I just SSH in for everything else. I run this stack both at home and work. It’s a good middle ground for me of stability and customizability.
@Fierro @selfhosted I mostly use YunoHost as I'm a beginner in self-hosting, but if needed I have command line. Ssh, then even one docker container or two. Mainly on Windows system with powershell or ordinary command line.
nothing wrong with yunohost. We all started out as noobs at one point in time. My advice though: Don't think that's the end point. Branch out when you have motivation/time/etc, and see what happens. The best way to learn is to break shit, then have to fix it. at least IMHO
@osanna The problem in breaking the system and building it back manually, is documentation.
I am a visually impaired person and many instructions are provided by screenshots.
I can't deny that lately AI has helped me through image description, but it allucinates often. So it means, AI or not, that for us (blind and visual impaired) a 5-minutes operation becomes one hour, and one hour becomes one day. Or week.
one thing i really really hate is videos/screenshots of instructions. I just want to read text damn it! i can only imagine how much more frustrating it is being visually impaired.
@osanna Especially when you have commands. I was born with commands as I used ms-dos at the beginning of 90s. But now, I honestly prefer something semi-automated for the "dirty" activities, as for configuration files it's very difficult to find the issue if you have a conf file made of dozens of lines, a long serie of indentations, punctuation signs and apostrophes everywhere, just forget one and you are screwed.
I'm not saying it's impossible, I'm saying that this can take double time of work, than an ordinary sighted administrator. I'm somehow envious of those who create a self-host platform on their very own, starting from a blank page.
view more: next ›