Co-op Cloud is a software stack that aims to make hosting libre software applications simple for small service providers such as tech co-operatives who are looking to standardise around an open, transparent and scalable infrastructure. It uses the latest container technologies and configurations are shared into the commons for the benefit of all.
Curious to hear what people think of the way it is build and it works vis-a-vis the way YNH works.
Supports hosting apps in subdirectories as well as subdomains.
Doesnât require a public-facing IP.
Supports system-wide mutualisation of resources for apps (e.g. sharing databases by default)
Cons
Upstream libre software communities arenât involved in packaging.
Uninstalling apps leaves growing cruft.
Limited to vertical scaling.
Not intended for use by hosting providers.
My 2 cts:
Thanks to them for the love.
Uninstalling apps leaves growing cruft.
If the app removal scripts does its job well, it should not leave cruft.
Limited to vertical scaling.
One day⢠with the friend-to-friend API.
Not intended for use by hosting providers.
True, but less true with Ansible deployment, I guess?
When I will have some time I will have a look to the their software. Their lack of screenshots tells me they are focused on the backend for the moment?
Nice of them to delve into the strengths and weaknesses of different platforms.
Then again, for who is it a disadvantage to have a home server platform that is not intended for use by hosting providers? Not in defense of perceived shortcomings, or to attack critique!
Friend-to-friend by the way, would be really cool for horizontal scaling
I think this comparative describe yunohost philosophy pretty much well. Of course i have some details to add, but itâs a good synthesis
Do you think those communities think they are not allowed to participate to this package ?
For me the true reasons is they doesnât want to spent time on packaging for x packaging format. So they do a docker image and thatâs it. However, we already have demonstrate that a generic container image couldânt feet several needs (like SSO integration, complexe backup policies or specific configuration panel).
I agree with them. YunoHost is not really made to be scaled over 500+ (maybe 1000) ynh accounts (with apps). Some things could be improved, some others wonât be. We are on a mono machine strategy, with all limitations that implied.
I think itâs false. YunoHost is not intended to be use to made Saas scalable services. But YunoHost is totally open to the idea of server provider preinstalling YunoHost. SOme of them scaleway, ikoula, ARN, or other providers has already integrated YunoHost on a part of their offersâŚ
Itâs a bit sad to not have libre.sh, sandstorm, ispconfig, freenas, plesk, umbrel and others.
I used to do stuff here and basically learned all the things that I do in Co-op Cloud by lurking YunoHost I would happily ammend this pros/cons list if people have strong feelings re: the hosting provider point. I tried to give the best overview I could but was not so deeply involved in this project after all⌠just a couple of months⌠lemme know!
Would gladly try to find a way to work together between the projects! Drop us a line @ boop AT autonomic DOT zone if you wanna chat or ping me herel Iâll re-enable mail notifications.
At my $day_job (autonomic) we were looking into offering managed YunoHost installs with an eye to contribute some % of the profit here but that hasnât worked out so far. Is anyone doing this already? One day hopefully!
Maybe âUninstalling apps leaves growing cruftâ is not really fair actually and could be removed?
âNot intended for use by hosting providersâ - I think this was coming from What is YunoHost? | Yunohost Documentation because of âa full VPS per user will be just fine, and we believe a better way to go.â which isnât really feasible for most hosting providers we have in mind?