Some FAQ shuffling
continuous-integration/drone/push Build is passing
Details
continuous-integration/drone/push Build is passing
Details
This commit is contained in:
parent
5ea705b34a
commit
e78e940044
20
docs/faq.md
20
docs/faq.md
|
@ -15,7 +15,12 @@ TODO.
|
||||||
|
|
||||||
## Which technologies are used?
|
## Which technologies are used?
|
||||||
|
|
||||||
TODO.
|
The core technologies are free software and enjoy wide adoption across free
|
||||||
|
software developer communities.
|
||||||
|
|
||||||
|
- [Containers](#why-do-you-use-containers)
|
||||||
|
- [Docker compose](#why-do-you-use-docker-compose)
|
||||||
|
- [Docker swarm](#why-do-you-use-docker-swarm)
|
||||||
|
|
||||||
## Who packages your applications?
|
## Who packages your applications?
|
||||||
|
|
||||||
|
@ -24,6 +29,19 @@ are already doing.
|
||||||
|
|
||||||
## Why do you use containers?
|
## Why do you use containers?
|
||||||
|
|
||||||
|
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
|
||||||
|
for their development and production environments. We can directly re-use this
|
||||||
|
good work for packaging and contribute back by helping maintain their
|
||||||
|
in-repository files. We meet them where they are at and we do not create a new
|
||||||
|
packaging format or duplicate effort. We tie our distribution directly into
|
||||||
|
existing developer Coop cloud is about re-using upstream free software project
|
||||||
|
container based workflows through well known CI/CD automation tools and issue
|
||||||
|
trackers. Coop cloud proposes the idea of more direct coordination between
|
||||||
|
distribution methods (app packagers) and production methods (developers).
|
||||||
|
|
||||||
|
## Why do you use Docker compose?
|
||||||
|
|
||||||
TODO.
|
TODO.
|
||||||
|
|
||||||
## Why do you use Docker Swarm?
|
## Why do you use Docker Swarm?
|
||||||
|
|
Loading…
Reference in New Issue