compose/local
Djordje Lukic 1f43b83409 Use a dependency graph to start services
The algorithm is like so:
* get all the leaves of the graph, these are all the service that don't have any dependency
* once a service is started we take the list of its parents (dependents)
* if all the dependencies of each of those dependents are started then we can start it as well
* if not then we continue to the next dependent

Signed-off-by: Djordje Lukic <djordje.lukic@docker.com>
2020-11-21 22:30:32 +01:00
..
e2e First local compose e2e tests 2020-11-20 18:06:11 +01:00
backend.go Fix linter errors 2020-11-18 17:18:41 +01:00
compose.go Use a dependency graph to start services 2020-11-21 22:30:32 +01:00
compose_test.go compose ps implementation 2020-11-19 13:34:43 +01:00
containers.go Target docker/docker 19.03 branch (api 1.40) 2020-11-17 13:28:58 +01:00
convergence.go Use a dependency graph to start services 2020-11-21 22:30:32 +01:00
convert.go Ensure extensions map is not nil (should be set by compose-go) 2020-11-19 13:10:55 +01:00
convert_test.go backend.local: Refactor conversion code 2020-11-04 09:54:29 +01:00
dependencies.go Use a dependency graph to start services 2020-11-21 22:30:32 +01:00
dependencies_test.go Run convergence in service dependency order 2020-11-19 13:10:13 +01:00
doc.go Update copyright 2020-09-22 12:13:00 +02:00
labels.go Local compose ls implementation 2020-11-19 09:48:54 +01:00
util.go apply linter recommendations 2020-11-19 17:35:34 +01:00
volumes.go backend.local: Add rudimentary volume support 2020-11-04 09:54:29 +01:00