coop-cloud/docs.coopcloud.tech
coop-cloud
/
docs.coopcloud.tech
4
1
Fork 14
Code Issues Pull Requests 2 Releases Activity

Fix typo
continuous-integration/drone/push Build is passing Details

This commit is contained in:
Luke Murphy 2021-02-23 17:21:46 +01:00
parent d96d9dd30c
commit 06a24601ea
No known key found for this signature in database
GPG Key ID: 5E2EF5A63E3718CC
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/overview.md
View File

@ -29,7 +29,7 @@ Learn more about why we use containers [in the FAQ section](faq/#why-containers)
The work required to take a new instance of an application and make it production ready is still too time intensive and often involves a duplication of effort. Each service provider needs to deal with the same problems: stable versioning, backup plan, secret management, upgrade plan, monitoring and the list goes on.
Therefore, the Co-op cloud proposes a packaing format which describes the entire production state of the application in a single place. This format is based on the [standards based compose specification] which is most commonly used by the [Docker compose] tool.
Therefore, the Co-op cloud proposes a packaging format which describes the entire production state of the application in a single place. This format is based on the [standards based compose specification] which is most commonly used by the [Docker compose] tool.
[Each application] that the Co-op cloud provides is described using the compose specification and makes use of the upstream project published container.