Djordje Lukic
4e9a4185af
Add `make lint` and run it on CI
|
5 лет назад | |
|---|---|---|
| .github | 5 лет назад | |
| azure | 5 лет назад | |
| backend | 5 лет назад | |
| cli | 5 лет назад | |
| client | 5 лет назад | |
| compose | 5 лет назад | |
| containers | 5 лет назад | |
| context | 5 лет назад | |
| example | 5 лет назад | |
| server | 5 лет назад | |
| util | 5 лет назад | |
| .dockerignore | 5 лет назад | |
| .gitignore | 5 лет назад | |
| .golangci.yml | 5 лет назад | |
| Dockerfile | 5 лет назад | |
| Makefile | 5 лет назад | |
| README.md | 5 лет назад | |
| builder.Makefile | 5 лет назад | |
| go.mod | 5 лет назад | |
| go.sum | 5 лет назад | |
| setup-dev.sh | 5 лет назад |
README.md
Docker API
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/[email protected]go get golang.org/x/tools/cmd/goimportsgo get gotest.tools/[email protected]go get github.com/golangci/golangci-lint/cmd/[email protected]
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.