Ulysses Souza 323601865d Test output of docker run
Signed-off-by: Ulysses Souza <ulyssessouza@gmail.com>
2020-05-13 17:09:18 +02:00
2020-05-13 10:44:04 +02:00
2020-05-13 10:44:04 +02:00
2020-05-05 17:14:26 +02:00
2020-05-13 10:44:04 +02:00
2020-05-12 12:04:57 +02:00
2020-05-13 10:44:04 +02:00
2020-05-13 10:50:36 +02:00
2020-05-13 10:44:04 +02:00
2020-05-13 17:09:18 +02:00
2020-04-24 15:03:46 +02:00
2020-04-24 14:04:27 +02:00
2020-05-06 15:56:47 +02:00
2020-05-05 10:50:30 +02:00
2020-05-12 13:46:26 +02:00
2020-05-12 13:46:26 +02:00
2020-05-13 10:44:04 +02:00
2020-05-06 12:18:53 +02:00

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.

Description
Define and run multi-container applications with Docker
Readme Apache-2.0 51 MiB
Languages
Go 97.1%
Dockerfile 2%
Makefile 0.5%
HCL 0.3%