[anderspitman]

This looks really nice.

In principle, I'm a big advocate of self-hosting (one of my services is even on this list). In practice, it just doesn't work for me. Once I get beyond 2-3 services it's just too much hassle to keep track of everything.

The key realization for me is that I don't actually care too much where the software is running, or who is running it for me. What I do care about is a avoiding vendor lock-in. As long as I have a reasonable escape hatch if my service company starts doing things I don't like, that's good enough. This keeps them honest. My issue with the current crop of monoliths like Google services is that there's no obvious migration path if you get fed up with them, so you're pretty much stuck with them no matter how crappy their software or customer service is/gets.

That's why I think something like sandstorm.io or cloudron is the future of self-hosting, at least in the near future. Maybe eventually we'll have a substrate of simple protocols and practices that will make it reasonable to manage everything yourself, but we're not there yet.

[bshipp]

I found docker was perfect for self-hosting services with relative ease. upgrades are self-contained, security is simplified behind a reverse proxy like nginx, and there are very few dependency conflicts to worry about. I've got about 40 containers running at any given time and barely think about them at all.

[BrandoElFollito]

Exactly my thought and setup.

I used to install and upgrade everything myself until I discovered docker and docker hub.

Together with watchtower I have zero maintenance on the versions and everything updates automatically.

[heavyset_go]

> Once I get beyond 2-3 services it's just too much hassle to keep track of everything.

Docker Swarm shines in this regard because it's easy to setup, and its simplicity allows you to just forget about it. I run 30+ services behind a reverse proxy for personal use and don't need to keep track of anything.