- cross-posted to:
- selfhosted@lemmy.world
- cross-posted to:
- selfhosted@lemmy.world
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?
You must log in or # to comment.
@jawsua we’re also on fediverse (here!) and Matix (links in bio) 👋 –3wordchant
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.
Yeah Im running Yunohost on a free Oracle cloud instance at the moment and a test instance on Rbpi at home. Im also working on (for last five years) home networking across the family locations (five houses in three countries)
Im still trying to sort out DNS for stuff sitting behind Dynamic IP ( Think I have got DDNS working with Hetzner for my own domain name) so next step is Yunohost locally with proper domain names rather than .local
Sometimes I do struggle being able to create test environments without impacting what I have got running live.
Of course Im also trying to rennovate and create a proper server cabinet and networking in the basement with UPS.
Im sure Ill have this done shortly before they pronounce me dead. /s
Must look at Proxmox - Don’t know anything about it.
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, not knocking it. If the tool suits the use case then have at it. Just never seen the appeal.
I have those same things. Reason I like proxmox over something else is I have full control. Had too many issues on things like TrueNAS scale where I had control taken away from me.
That’s also what they said about Dropbox: https://news.ycombinator.com/item?id=9224
Okay?
I think this, like anything tech, depends on the usecase.
As an example, if I was an ethnographer working to document rural cooking techniques on the Isle of Skye I might work with this group to stand up a public instance of mealie. Success would depend on the project being a collective work though. Me working with the collectives to meet the challenges of the project over a loosely defined set of time.
I think the above could be a big success. On the opposite side, I would not count on the collective to host and maintain my personal tech stack. Maybe I’d pay them to advise, but little more
These are different things. This project is more like a guide to running things kind of manually with their toolset they’ve constructed.
CasaOS is really based around the UI.
Cosmos is more about a desktop-like admin interface that can import CasaOS recipes or whatever they call them. Seems to also support multiple users and have some host tuning that Casa lacks.
It just depends on which route you want to go.
Yeah, I know they’re different. I was just giving some background about what was going on, sorry if I confused.
Just wondering if anyone has used what seems to be their compose/swarm config tool “abra”, especially multiserver, and have any feedback about it. I like that it seems to be pretty agnostic after doing its work, they say you can backup and export the config and use it elsewhere mostly as-is. Just can’t see much anywhere else about it.
@jawsua at least a couple of organisations are using co-op cloud in production with multiple servers (we have about 25 servers we’re managing at @autonomic ). There’s at least one group using co-op cloud “recipes” (app configs) without
abra, the recipe collection / commandline tool / organising federation are intended to be useful as three separate pieces, as well as combined –3wordchant
