forked from coop-cloud/docs.coopcloud.tech
Trim intro and add FAQ
This commit is contained in:
parent
8f55dca758
commit
c59ad0b751
|
@ -0,0 +1,57 @@
|
||||||
|
---
|
||||||
|
title: Frequently Asked Questions
|
||||||
|
---
|
||||||
|
|
||||||
|
## What is the Cooperative Cloud?
|
||||||
|
|
||||||
|
The Cooperative Cloud is a platform built by and for worked-owned technology
|
||||||
|
cooperatives which proposes a shared social and technical infrastructure for
|
||||||
|
the operation and management of free software applications.
|
||||||
|
|
||||||
|
## What about <insert-your-favourite-alternative\>?
|
||||||
|
|
||||||
|
### Cloudron
|
||||||
|
|
||||||
|
- 👍 Lovely web interface for application, domain & user management
|
||||||
|
- 👍 Bigger library of applications
|
||||||
|
- 👍 Built-in SSO using LDAP, which is compatible with more applications and often has a better user interface than OAuth
|
||||||
|
- 👍 Most applications are actively maintained by the Cloudron team
|
||||||
|
- 👎 Moving away from open source. Free version has a 1-application limit
|
||||||
|
- 👎 Based on Docker images, not stacks, so multi-process applications (e.g. parsoid for Mediawiki) are a non-starter
|
||||||
|
- 👎 Difficult to extend applications
|
||||||
|
- 👎 Only supported on Ubuntu
|
||||||
|
- 👎 Upstreams free software communities aren't involved
|
||||||
|
|
||||||
|
### YunoHost
|
||||||
|
|
||||||
|
- 👍 Lovely web interface for application, domain & user management
|
||||||
|
- 👍 Bigger library of applications
|
||||||
|
- 👍 Awesome backup / deploy / restore continuous integration testing
|
||||||
|
- 👍 Supports hosting applications in subdirectories as well as subdomains
|
||||||
|
- 👍 Doesn't require a public-facing IP
|
||||||
|
- 👎 Upstreams free software communities aren't involved
|
||||||
|
- 👎 Often not idempotent: uninstalling applications leaves growing cruft
|
||||||
|
|
||||||
|
### Ansible
|
||||||
|
|
||||||
|
- 👍 Includes server creation and bootstrapping
|
||||||
|
- 👎 Upstream free software communities aren't publishing Ansible roles
|
||||||
|
- 👎 Lots of manual work involved in things like application isolation, backups, updates
|
||||||
|
|
||||||
|
### Kubernetes
|
||||||
|
|
||||||
|
- 👍 Helm charts are available for some key applications already
|
||||||
|
- 👎 Too big -- requires 3rd party tools to run a single-node instance
|
||||||
|
|
||||||
|
### Docker-compose
|
||||||
|
|
||||||
|
- 👎 Manual work required for process monitoring
|
||||||
|
- 👎 Secret storage not available yet
|
||||||
|
- 👎 [Swarm is the new best practice](https://github.com/BretFisher/ama/issues/8#issuecomment-367575011)
|
||||||
|
|
||||||
|
### Doing it Manually
|
||||||
|
|
||||||
|
- 👍 Simple - just follow upstream instructions to install and update
|
||||||
|
- 👎 Loads of manual work required for application isolation and backups
|
||||||
|
- 👎 Array of sysadmin skills required to install applications
|
||||||
|
- 👎 Hard to share configurations into the commons
|
|
@ -9,27 +9,17 @@ initiated by [Autonomic].
|
||||||
|
|
||||||
The project arose out of the understanding that technology cooperatives
|
The project arose out of the understanding that technology cooperatives
|
||||||
continue to struggle to deliver free software solutions without relying on
|
continue to struggle to deliver free software solutions without relying on
|
||||||
monopolies such as Google, Microsoft and Amazon for technical infrastructure
|
monopolies such as Google, Microsoft and Amazon for technical infrastructure.
|
||||||
and software tools. The contradictions of working with these abusive and
|
The contradictions of working with abusive and extractive forces brings the
|
||||||
extractive forces brings the idea of offering an alternative into question.
|
idea of offering an alternative into question.
|
||||||
|
|
||||||
[The technological crisis is a social crisis]. Therefore, building an
|
[The technological crisis is a social crisis] and therefore building an
|
||||||
alternative digital future cannot be done without broad and meaningful
|
alternative digital future cannot be done without broad and meaningful
|
||||||
cooperation. The Cooperative Cloud project takes as its starting point, the
|
cooperation. The Cooperative Cloud project takes as its starting point, the
|
||||||
independent free software community standards, tools, approaches and governance
|
independent free software community standards, tools, approaches and governance
|
||||||
methods which cooperatives can make use of as part of offering a real
|
methods which cooperatives can make use of as part of offering a real
|
||||||
alternative.
|
alternative.
|
||||||
|
|
||||||
The Cooperative Cloud should not be seen as a technical solution for a social
|
|
||||||
problem (i.e. "Big Tech"). We understand that owning the common technological
|
|
||||||
means for delivering free software is only one part of the struggle to reclaim
|
|
||||||
technology today. If antitrust litigation dismantled the monopolies tomorrow,
|
|
||||||
we'd need our own organisations and robust technical capacity to fill the
|
|
||||||
resulting vacuum. From this perspective, the project can be seen as another
|
|
||||||
approach to building community power by focussing on the cooperative ways and
|
|
||||||
means of managing the free software applications on which so much of our lives
|
|
||||||
have come to rely on.
|
|
||||||
|
|
||||||
To learn more, please see the [Getting Started guide].
|
To learn more, please see the [Getting Started guide].
|
||||||
|
|
||||||
[autonomic]: https://autonomic.zone/
|
[autonomic]: https://autonomic.zone/
|
||||||
|
|
|
@ -1,37 +0,0 @@
|
||||||
# "This is foolishness, what about ...?"
|
|
||||||
|
|
||||||
- Kubernetes
|
|
||||||
- 👍 Helm charts are available for some key apps already
|
|
||||||
- 👎 too big -- requires 3rd party tools to run a single-node instance
|
|
||||||
- Bitnami stacks
|
|
||||||
- Cloudron
|
|
||||||
- 👍 Lovely web interface for app, domain & user management
|
|
||||||
- 👍 Bigger library of apps
|
|
||||||
- 👍 Built-in SSO using LDAP, which is compatible with more apps and often has a better user interface than OAuth
|
|
||||||
- 👍 Most apps are actively maintained by the Cloudron team
|
|
||||||
- 👎 Moving away from open source. Free version has a 1-app limit
|
|
||||||
- 👎 Based on Docker images, not stacks, so multi-process apps (e.g. parsoid for Mediawiki) are a non-starter
|
|
||||||
- 👎 Difficult to extend apps
|
|
||||||
- 👎 Only supported on Ubuntu
|
|
||||||
- 👎 Upstreams aren't involved
|
|
||||||
- Yunohost
|
|
||||||
- 👍 Lovely web interface for app, domain & user management
|
|
||||||
- 👍 Bigger library of apps
|
|
||||||
- 👍 Awesome backup / deploy / restore continuous integration testing
|
|
||||||
- 👍 Supports hosting apps in subdirectories as well as subdomains
|
|
||||||
- 👍 Doesn't require a public-facing IP
|
|
||||||
- 👎 Upstreams aren't involved
|
|
||||||
- 👎 Not idempotent: uninstalling apps leaves growing cruft
|
|
||||||
- Ansible
|
|
||||||
- 👍 Includes server creation and bootstrapping
|
|
||||||
- 👎 Upstreams aren't publishing Ansible roles
|
|
||||||
- 👎 Lots of manual work involved in things like app isolation, backups, updates
|
|
||||||
- `docker-compose`
|
|
||||||
- 👎 Manual work required for process monitoring
|
|
||||||
- 👎 Secret storage not available yet
|
|
||||||
- 👎 [Not recommended](https://github.com/BretFisher/ama/issues/8)
|
|
||||||
- Manually installing apps
|
|
||||||
- 👍 Simple - just follow upstream instructions to install and update
|
|
||||||
- 👎 Loads of manual work required for app isolation and backups
|
|
||||||
- 👎 Array of sysadmin skills required to install apps
|
|
||||||
- 👎 Hard to share configs into the commons
|
|
Loading…
Reference in New Issue