I used to use this, but I've grown disillusioned with these sorts of self-hosting admin tools that try to be user friendly.
It's great when everything works, but under the hood Yunohost is running a bunch of scripts to e.g. manage distro packages. When that fails, you often can't recover through the UI in my experience and you then have to work out what the fancy tools were trying to do under the hood so you can log in and fix it yourself. After a few iterations of that I decided it wasn't worth the hassle.
The only one I still use is Sandstorm, because it's more of a container-based system and doesn't rely on scripts that can fail and leave the system in a half-finished state. Its userbase is unfortunately much smaller though, so the package selection isn't nearly as good. For the packages that are there though it's been pretty rock solid.
It can be, but one of the biggest draws to things like Sandstorm and Yunohost is that they handle auth for you. I run a bit of Dockerized infra too but managing users for a bunch of services separately is kind of a pain. You can set up central auth yourself but as a lone sysadmin that's even more of a pain :)
Fair. Could an auth solution for proxmox not exist? Or Sandstorm/Yunohost run within proxmox?
I remember seeing a Github repo where someone had baked all the proxmox install and maintenance scripts using rockylinux including auth. Much cleaner than I would organically end up at without reinstalling :)
Mostly TTRSS with a bit of DokuWiki, Etherpad, and Davros. I was using Radicale but wanted more email/calendar integration, and I was using the WordPress app for my local hackerspace but its static site generation took too long for our very large website.
I've been looking at the WordPress package lately and I definitely think there is room for improvement. For one, publishing seems to create a complete duplicate copy of all of the media, which is super painful for large sites.
Yeah - that and the lack of feedback when generating the static files. It's fine when it's a small site and generation finishes ~immediately, but when it's going to take a while it'd be helpful to have some indication that things are happening and when they finish.
It's great when everything works, but under the hood Yunohost is running a bunch of scripts to e.g. manage distro packages. When that fails, you often can't recover through the UI in my experience and you then have to work out what the fancy tools were trying to do under the hood so you can log in and fix it yourself. After a few iterations of that I decided it wasn't worth the hassle.
The only one I still use is Sandstorm, because it's more of a container-based system and doesn't rely on scripts that can fail and leave the system in a half-finished state. Its userbase is unfortunately much smaller though, so the package selection isn't nearly as good. For the packages that are there though it's been pretty rock solid.