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?
I’ve never seem the appeal of any if these sorts of solutions. It’s really easy to just spin up proxmox then build an lxc.
Eh, it is what it is. I have a full family life and a job screwing with computers all week. I don’t want to deal with spinning up, troubleshooting, and maintaining a mini devops stack.
I don’t want to spend so much personal time to keep up with all the management and config, but I don’t think that means someone like me should have to live in a big tech world. If there’s a good framework that helps keep things easy to manage and secure for a minimal amount of input and time, even if I could run most of it myself manually with a lot more time investment, there’s no reason not to, IMHO.
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.