rix/docs.coopcloud.tech
0
0
Fork 0
forked from toolshed/docs.coopcloud.tech
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Shorten FAQ questions

Browse Source
This commit is contained in:
Luke Murphy
2021-02-23 17:15:41 +01:00
parent 8234293074
commit 89dabeb08f
2 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/faq.md
View File

@ -6,7 +6,7 @@ title: Frequently asked questions
The Co-op Cloud is a project which aims to make self-hosting free software applications simple! It's a project which fits in alongside others like [Cloudron](https://www.cloudron.io/), [Yunohost](https://yunohost.org/) and [Freedombone](https://freedombone.net/) and others but has its own specific focus. The project is intended for existing small service providers and cooperatives already involved in hosting work who are looking for alternatives. The Co-op Cloud is a project which aims to make self-hosting free software applications simple! It's a project which fits in alongside others like [Cloudron](https://www.cloudron.io/), [Yunohost](https://yunohost.org/) and [Freedombone](https://freedombone.net/) and others but has its own specific focus. The project is intended for existing small service providers and cooperatives already involved in hosting work who are looking for alternatives.
## Which technologies are used? ## Which technologies?
The core technologies are free software and enjoy wide adoption across free The core technologies are free software and enjoy wide adoption across free
software developer communities. software developer communities.
@ -20,7 +20,7 @@ software developer communities.
One of your main aims is to re-use existing work that free software communities One of your main aims is to re-use existing work that free software communities
are already doing. are already doing.
## Why do you use containers? ## Why containers?
We use containers because so many free software communities choose to use them! We use containers because so many free software communities choose to use them!
They are already writing and using Docker files and Docker-compose definitions They are already writing and using Docker files and Docker-compose definitions
@ -33,9 +33,9 @@ container based workflows through well known CI/CD automation tools and issue
trackers. Coop cloud proposes the idea of more direct coordination between trackers. Coop cloud proposes the idea of more direct coordination between
distribution methods (app packagers) and production methods (developers). distribution methods (app packagers) and production methods (developers).
## Why do you use Docker compose? ## Why Docker Compose?
## Why do you use Docker Swarm? ## Why Docker Swarm?
## Why start another project? ## Why start another project?
@ -118,6 +118,6 @@ We have our critiques of other similar projects which are already up-and-running
- 👎 Array of sysadmin skills required to install applications - 👎 Array of sysadmin skills required to install applications
- 👎 Hard to share configurations into the commons - 👎 Hard to share configurations into the commons
## What licensing model does the project use? ## What licensing model do you use?
The Co-op Cloud will always be available under copyleft licenses. The Co-op Cloud will always be available under copyleft licenses.

6
docs/overview.md
View File

@ -15,7 +15,7 @@ Applications that you may already use in your daily life: [Nextcloud], [Jitsi],
The communities who develop these softwares also publish them using containers. For example, here is the [Nextcloud hub.docker.com account] which allows end-users to quickly deploy a new Nextcloud instance. The communities who develop these softwares also publish them using containers. For example, here is the [Nextcloud hub.docker.com account] which allows end-users to quickly deploy a new Nextcloud instance.
Learn more about why we use containers [in the FAQ section](faq/#why-do-you-use-containers). Learn more about why we use containers [in the FAQ section](faq/#why-containers).
[nextcloud]: https://nextcloud.com [nextcloud]: https://nextcloud.com
[jitsi]: https://jitsi.org [jitsi]: https://jitsi.org
@ -33,7 +33,7 @@ Therefore, the Co-op cloud proposes a packaing format which describes the entire
[Each application] that the Co-op cloud provides is described using the compose specification and makes use of the upstream project published container. [Each application] that the Co-op cloud provides is described using the compose specification and makes use of the upstream project published container.
Learn more about why we use Docker compose [in the FAQ section](faq/#why-do-you-use-docker-compose). Learn more about why we use Docker compose [in the FAQ section](faq/#why-docker-compose).
[standards based compose specification]: https://compose-spec.io [standards based compose specification]: https://compose-spec.io
[docker compose]: https://docs.docker.com/compose/ [docker compose]: https://docs.docker.com/compose/
@ -45,7 +45,7 @@ Once we have our application packaged, we need a deployment environment. Product
The Co-op cloud makes use of [Docker swarm] as a deployment environment. It offers an approriate feature set which allows us to support zero-down time upgrades, seamless application rollbacks, automatic deploy failure handling, scaling, hybrid cloud setups and maintain a decentralised design. The Co-op cloud makes use of [Docker swarm] as a deployment environment. It offers an approriate feature set which allows us to support zero-down time upgrades, seamless application rollbacks, automatic deploy failure handling, scaling, hybrid cloud setups and maintain a decentralised design.
Learn more about why we use Docker swarm [in the FAQ section](faq/#why-do-you-use-docker-swarm). Learn more about why we use Docker swarm [in the FAQ section](faq/#why-docker-swarm).
[docker swarm]: https://docs.docker.com/engine/swarm/ [docker swarm]: https://docs.docker.com/engine/swarm/