I highly recommend yunohost. I am using it since a few years, after a lot of years of maintaining my own "classic" mail + web server by hand [1].

I deploy it in an unprivileged LXC container [2] and went through several upgrades already. It really worked great for me.

[1] https://benou.fr/www/ben/14-years-of-self-hosting.html [2] https://github.com/bganne/yunohost

Is that read: "Why You No Host? dot org"

Indeed it is: https://yunohost.org/user/images/dude_yunohost.jpg

Love it!

A visit to the home page will give you the delightful answer

It isnt based on docker, so it heavily depends on unofficial packages.

I hate how it's just a drive-by criticism now that something isn't using Docker.

You know we weren't in the dark ages before Docker, right?

Not the OP, but while I would have no problem using an orchestrator based on a different common packaging than Docker (e.g. RPM or AppImage), I would be very hesitant to use one that needs its own bespoke packaging. Because that's maintenance work and I would need to feel confident that someone will keep packaging future app updates.

Comparatively speaking, going back to how we deployed applications 10 years ago is the dark ages. Having everything in containers is objectively easier both from a getting started and ongoing maintenance standpoint.

Now: making minimal edits to a provided compose file for initial configuration, run command to spin up everything application needs, and you're done.

Then: install application package onto system (best: from developer package source/better: from old version in operating system repo/worst: by compiling from source after locating all dependencies and running make install), setting up any necessary databases or storage by hand, editing configuration files that are hopefully in /etc if the developer thinks the FHS is something to be honored, setting up init scripts/unit files so the application starts up in the environment it wants and when you want, and finally running the command which starts the application (which is probably distro specific).

And that's not even getting into updates. I'll take pulling the latest version of the container and restarting over app specific update instructions any day of the week. Life is too short for putting up with that kind of minutia.

I played with YunoHost a bit yesterday, and within a couple of hours hit a situation where a misbehaving application froze the whole thing requiring a reboot. That's after spending longer than I wanted figuring out why the ISO always locked up mid-install, starting with Debian 11 + nonfree drivers instead and installing Yuno on top.

Really liked the concept, not the execution so much as it turns out.

Thinking of taking a look at CapRover next, which is docker based. This Tipi thing might be worth a go too, though maybe when it's a bit more mature.

You'll like some of the apps available on CapRover, like PenPot. I've used CR several times just for a few apps they supply.

Its the technobro version of “I have to install this instead of just downloading it off the app store?? Nah brah.”

Better analogy would be:

"I have to download F-Droid, compile it, and then install your app? Nah brah."

yes we were

Yep and thusly also turns into somewhat of a spaghetti monster.

Wow, that UI is basically the endstate of tile UI. All you get is a pastel color and two letters? What do they call that cult? Material Design?

That is SCREAMING for iPhone 1.0 style icons. There was just an HN post on how crappy modern icons are, I think it was the "there is no personality in 2020". This would be Exhibit A.

I gave it a try some months ago, and it was quite disappointing. The amount of broken packages was strange, and the number of problems with their Interface was slightly disappointing.

But true, if you can work past those things, it might be better than tipi.

Came here looking for this reference. A comparison table with existing similar projects would be nice.