For me it is writting docker compose files describing my services. I like to test them on my machine before pushing them to the server(s). But I guess that’s my own fault for not using something like portainer or even SSHFS.
What’s the most annoying / painful step for you?
Managing docker-compose files over a few servers.
Notepad++ is fantastic, I can have multiple tabs with docker-compose files from different servers (via a ssh plugin), in a single window.
I was advised to move to VSCode or VSCodium. Neither can handle a single window with files from different servers, I need to switch workspace every time. Back to Notepad++.
You can have a central repo for your files. I have a different folder for each server. VSCode has access to these folders to edit any data needed.
Most of the compose files are managed in Portainer, but some of the containers need to exist outside of Portainer.
You absolutely can mount different files from different servers simultaneously in vscode. I do it all the time with the SSHFS plugin. You just set the server, login, and path, then you can the remote folder to any workspace, and you can mount multiple different folders simultaneously. Right now I have a workspace which has mounted folders from 3 different servers for my Grafana/Prometheus/Influx DB setup
You absolutely can mount different files from different servers simultaneously in vscode
It’s not in vscode then, it is on the filesystem if I understand correctly. Then even notepad can handle that.
sshfs causes weird permission issues for every server I use and cannot save files, so that’s not an option.
I’m sorry what? You can edit text files on a different machine from notepad++??? Omg this changes… everything. Wtf I did not know this. How could not have known this!!!
I actually was a Notepad++ fanatic for years and still use it lightly but I have made the switch to VSCode about 6 months ago and I’ll never look back. As the other commenter said you absolutely can mount files from multiple workspaces as well. Hell you can even copy files between file systems.
Buying good equipment
Utilizing it properly
In my experience, it’s the noise and cable management.
The rack we chose was a cheapo open-frame off Amazon so all the cables are kind of just hanging off the side while only being partially tied up and run through loops made of zip ties. Proper loops, wire arms, drawers, etc, are expensive to obtain in this area, and we’ve moved to the rack several times over the past several years. We’ve also lost a few bolts because they literally snap off while being removed.
Yes, having worked in server rooms before setting up home equipment, I chose to use consumer grade equipment. Less noise, less heat, potentially less power. My first “rack” was a wooden storage rack to hold the then 3 desktop towers. I did get the fun of building each system from scratch to get the specific bang for the buck.
Welp, everyone beat me to the dad jokes.
designing, spending money on a setup, only to find out I need to scale more 6 months later and realizing that overhauling the current setup is not gonna work leading to basically building a new homelab all over again.
Dropping a machine on my foot
Having a friend drop an crazy heavy enterprise class server on your leg…
Cabling. Has to be cabling. It is the only thing I don’t enjoy. More specifically, cabling the whole home.
Learning that you don’t have enough upload to do everything you want….
Finding space
Backup
Shelling out for it, and the ongoing costs.
Electricity might be “cheap” in amreica. But in the Real world, selfhosted costs real money that takes from other necessities like heating/cooling.
Don’t try to bullshit me, power is expensive in AU, and Heat/Cool is regularly on.
My quarterly with a VERY modest system, and really taxing rules on power (read using AC/HEATING) and my quarters are still $600AUD.
Hope you have a good paying job, or live in a country that doesn’t give a shit about power costs.
Documentation. Like proper documentation.
Cable management
Editing other peoples’ docker compose or dockerfiles to suit my needs.