@autonomic This looks really cool! i noticed something that was a bit confusing in the getting started guide - the section with the example Nextcloud deployment has different domains in different commands.
Here's what we've written so far on that ^^
A interesting thing to note is that you can do compartmentalisation in any way you want. You could have one app per VPS or a separate VPS per client etc. It's really up to you.
@handle @kawaiipunk @autonomic
Yeah so what I want to know is “are their formal policies for how the people running the underlying infrastructure operate and behave”. This isn’t a question about guest security, I’m asking about the host level controls. Think of it like I’m asking for a SOC-2 type 2.
Co-op Cloud doesn't currently have "people running the infrastructure", at this point it's a software project rather than an organisation that provides hosting services.
Autonomic, the group that's launched Co-op Cloud, does host services using Co-op Cloud (including some of the Co-op Cloud infrastructure), and like @kawaiipunk says that information isn't published yet.
@autonomic this is great, something i've been dreaming about :) unfortunately, in-dream-version was #ansible with debops.org (which would help with publishing and sharing roles, one of the cons for ansible you point out). that would also keep the #debian package as the packaging unit instead of docker images. this would be a simpler architecture. would require the implementation of the cluster/ha logic in ansible, but it'd be leaner and more modular and reusable, i think.
Sunbeam City is a anticapitalist, antifascist solarpunk instance that is run collectively.