- cross-posted to:
- selfhosted
- cross-posted to:
- selfhosted
I’ve been searching for a replacement for my crufty Yunohost install, something that runs docker, “app” install, and preferably SSO and multiuser. I was deciding between CasaOS and Cosmos Cloud when I stumbled on Co-Op Cloud. I can’t find anything on it online anywhere except for their site. Anyone tried it or have any opinions?
Hey … I have been looking at both. Im a Business Analyst rather than DevOps so I went for Yunohost.org as it got me something running more quickly rather than Coop.Cloud but I can see the different use cases.
Can I ask why you described your install as Crufty? What issues have you run into hauving Yunohost for a while?
It feels to me (Without direct experience running Coop Cloud bit more looking and chatting ) that its more aimed at provisioning multiple instances for multiple customers across multiple VMs rather than Yunohost which seems like more of a - This is one instance on one server/VM
There is a part of me that likes the user admin features/ GUI of Yunohost and wonders whether people managing multiple organisations across many VMs would want to wrap Yunohost inside Coop. Cloud - but im all new to this.
I’ve had Yunohost running in some way for probably 4+ years? It’s relatively solid, I can mostly depend on it without any issues. I like the SSO/LDAP user auth and perms, and the default fail2ban and ability to change ssh port from the UI. The update and system services pages are nice.
What I don’t like is how apps are all installed locally instead of using containers or VMs. And resources are shared, so if one app uses, for instance, MongoDB, and another app needs it as well, they have to share the same one. It makes things run a bit leaner, but I do worry a bit about data bleed if there’s some vulnerability. And the apps are really hit and miss, since they have to be packaged, managed, and issue-tracked independently for this platform instead of the main app/project. So you find lots of orphaned or half-maintained apps that should be great otherwise.
So you either suck it up and deal, or become a bit of a hacker/maintainer yourself on apps you care the most about. But if I wanted to get that involved I’d just roll a manual build myself. I submit issues and try to help where I can, but that’s not where I want to be.
You could probably install something like Portainer and manually edit the NGINX config/homepage to hack some docker in there, but idk if I care enough to do that.
Cool really useful feedback. I really like the SSO/LDAP user auth and perms and its cool that it includes email. Im not sure how that is going to go but hey lets find out eh?
I can see the downsides you mentioned and yeah I guess that I am going to run into them as I have more of the family using the instance.
Do you think we will end up with some kind of Yunohost / Coop.Cloud Hybrid where you fan start simple and then if you grow move to a containerised / multiple server environment?
I had sort of thought Coop Cloud was more about managing multiple customers ( but I can see architecturally it is also better able to scale for a single customer. it just feels a shame its a separate project rather than an extension/ evolution of Yunohost. (The BA in me asks could Yunohost be an application inside Coop Cloud to start )
If you’re wanting to do something like that, you’re probably best running Proxmox as a bit of a hypervisor, then Yunohost in a Debian VM on top, and assign something like “home.domain.tld” to Yunohost and get your “stable” family services running.
Then you can try out other stuff like Coop, Cosmos, OMV, Caprover, Tipi, etc as other VMs if you wanna try adding something Yunohost can’t or doesn’t do well. Or if you wanna extend your DevOps skills without messing up family-prod. I mean, you could even have another Yunohost as a “sandbox.domain.tld” before new service deploy.