Define and run multi-container applications with Docker
Go to file
Djordje Lukic fe1772b84a Moby backend 2020-05-11 15:49:03 +02:00
.github/workflows First e2e tests running locally (with example backend) 2020-05-05 14:40:30 +02:00
azure ACI Container ids work fine between ps, log & exec, either from single container (docker run) of multi-container compose stack 2020-05-06 22:15:33 +02:00
backend Refactor example/backend 2020-05-05 17:14:26 +02:00
cli Moby backend 2020-05-11 15:49:03 +02:00
client Refactor example/backend 2020-05-05 17:14:26 +02:00
compose Add compose up and down 2020-05-05 14:03:14 +02:00
containers Refactor on services 2020-05-05 15:37:12 +02:00
context Add `make lint` and run it on CI 2020-05-05 10:50:30 +02:00
example Refactor example/backend 2020-05-05 17:14:26 +02:00
moby Moby backend 2020-05-11 15:49:03 +02:00
server Refactor on services 2020-05-05 15:37:12 +02:00
tests Moved sample compose files in test folder 2020-05-07 09:35:25 +02:00
util Add `docker context create` command 2020-04-26 19:42:20 +02:00
.dockerignore Add dockerignore 2020-04-24 15:03:46 +02:00
.gitignore Remove non-project path 2020-04-24 14:04:27 +02:00
.golangci.yml Add ACI compose basic e2e test 2020-05-06 15:56:47 +02:00
Dockerfile Add `make lint` and run it on CI 2020-05-05 10:50:30 +02:00
Makefile Added aci e2e tests, not run in CI since requiring azure login. 2020-05-06 15:48:01 +02:00
README.md Implement quiet flag for ps command 2020-05-06 12:18:53 +02:00
builder.Makefile Add `make lint` and run it on CI 2020-05-05 10:50:30 +02:00
go.mod Moby backend 2020-05-11 15:49:03 +02:00
go.sum Moby backend 2020-05-11 15:49:03 +02:00
setup-dev.sh Use github action to install protoc 2020-04-30 17:45:48 +02:00

README.md

Docker API

Actions Status

Dev Setup

The recommended way is to use the main Makefile that runs everything inside a container.

If you don't have or want to use Docker for building you need to make sure you have all the needed tools installed locally:

  • go 1.14
  • go get github.com/golang/protobuf/protoc-gen-go@v1.4.1
  • go get golang.org/x/tools/cmd/goimports
  • go get gotest.tools/gotestsum@v0.4.2
  • go get github.com/golangci/golangci-lint/cmd/golangci-lint@v1.26.0

And then you can call the same make targets but you need to pass it the builder.Makefile (make -f builder.Makefile).

Building the project

$ make

If you make changes to the .proto files, make sure to make protos to generate go code.

Tests

To run unit tests:

make test

If you need to update a golden file simply do go test ./... -test.update-golden.