←back to thread

Self-Hosting like it's 2025

(kiranet.org)
221 points finnlab | 1 comments | 01 Apr 25 10:11 UTC | HN request time: 0s | source
Show context
bauerd ◴[01 Apr 25 11:20 UTC] No.43545430[source]▶
Last thing I need is Kubernetes at home
replies(11): >>43545448 #>>43545480 #>>43545584 #>>43545606 #>>43545610 #>>43545648 #>>43545656 #>>43545661 #>>43548737 #>>43550543 #>>43552457 #
raphinou ◴[01 Apr 25 11:53 UTC] No.43545661[source]▶
Exactly, my first reaction was "I should write a blog post about why I still use Docker Swarm". I deploy to single node swarms, and it's a zero boiler plate solution. I had to migrate services to another server recently, and it was really painless. Why oh why doesn't Docker Swarm get more love (from its owners/maintainers and users)?....

Edit: anyone actually interested in such a post?

replies(9): >>43545769 #>>43545842 #>>43546429 #>>43546455 #>>43546541 #>>43547576 #>>43549257 #>>43549367 #>>43549757 #
gmm1990 ◴[01 Apr 25 13:14 UTC] No.43546429[source]▶
I'd be interested. Might be a strange question but I'll throw it out there, I seem to have a hard time finding a good way to define my self hosted infrastructure nodes and which containers can run on them, have you run into/have a solution for this? Like I want my database to run on my two beefier machines but some of the other services could run on the mini pcs.
replies(1): >>43547536 #
1. raphinou ◴[01 Apr 25 14:55 UTC] No.43547536{3}[source]▶
I am running one-node swarms, so everything I deploy is running on the same node. But from my understanding you can apply labels to the nodes, and limit the placement of containers. See here for an example (I am not affiliated to this site): https://www.sweharris.org/post/2017-07-30-docker-placement/