silva
/
compose
mirror of https://github.com/viniciusfdasilva/compose.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
Define and run multi-container applications with Docker
449 Commits 1 Branch 0 Tags 13 MiB
Go 96.8%
Dockerfile 2.2%
Makefile 0.6%
HCL 0.3%
Go to file
Guillaume Tardif f403307edf Allow compose updates without having to delete the stack every time. 
Update will “typically” keep the same IP, but this isn’t guaranteed by azure
(ACI has limitations on what can be updated, but this does not apply to us for the moment : https://docs.microsoft.com/en-us/azure/container-instances/container-instances-update#properties-that-require-container-delete)
For the moment I check in the test that the IP is keep the same
 		2020-06-18 10:03:28 +02:00
.dependabot Run dependabot daily instead of weekly 2020-06-09 09:45:57 +02:00
.github Build example and local backend conditionaly 2020-06-15 18:02:30 +02:00
azure Allow compose updates without having to delete the stack every time. 2020-06-18 10:03:28 +02:00
backend Remove unused backend proto 2020-06-02 09:41:57 +02:00
cli Merge pull request #228 from docker/compose_project_name 2020-06-17 05:52:55 -07:00
client Store context type in metadata to make retrocompatibility with previous contexts easier (potentially switching back and forth) 2020-06-10 18:17:48 +02:00
compose Removed unnecessary test 2020-06-17 14:13:28 +02:00
config Renamed Moby backend to “local” backend. This will leave “moby” available for default type contexts 2020-06-15 12:20:03 +02:00
containers Add inspect command 2020-06-15 15:08:04 +02:00
context default context type is “moby” 2020-06-15 12:25:35 +02:00
docs/cli Renamed Moby backend to “local” backend. This will leave “moby” available for default type contexts 2020-06-15 12:20:03 +02:00
errdefs Change the way a context is stored 2020-05-22 16:32:43 +02:00
example Merge pull request #205 from ulyssessouza/inspect 2020-06-16 09:33:33 +02:00
formatter Add --json option to commands 2020-06-17 10:00:42 +02:00
local Relax constraints on flaky tests (due to // runs) 2020-06-17 08:58:24 +02:00
multierror Add multierror 2020-05-13 18:37:41 +02:00
protos Add tests on inspect 2020-06-15 17:20:37 +02:00
server Merge pull request #221 from rumpl/feat-context-metadata 2020-06-16 00:43:36 -07:00
tests Allow compose updates without having to delete the stack every time. 2020-06-18 10:03:28 +02:00
.dockerignore Add .git to .dockerignore 2020-05-29 11:29:28 +02:00
.gitattributes Removed test requiring linux containers 2020-06-11 12:58:58 +02:00
.gitignore Remove non-project path 2020-04-24 14:04:27 +02:00
.golangci.yml Extract interface / types to allow unit tests / mock 2020-05-15 10:15:56 +02:00
Dockerfile Build example and local backend conditionaly 2020-06-15 18:02:30 +02:00
Makefile Build example and local backend conditionaly 2020-06-15 18:02:30 +02:00
README.md Build example and local backend conditionaly 2020-06-15 18:02:30 +02:00
builder.Makefile Build example and local backend conditionaly 2020-06-15 18:02:30 +02:00
go.mod Bump github.com/Azure/azure-sdk-for-go 2020-06-17 12:57:18 +00:00
go.sum Bump github.com/Azure/azure-sdk-for-go 2020-06-17 12:57:18 +00: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
  • protoc
  • go get github.com/golang/protobuf/protoc-gen-go@v1.4.1
  • go get golang.org/x/tools/cmd/goimports
  • 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).

The new CLI delegates to the classic docker for default contexts ; delegation is done to docker-classic.

  • make classic-link will create a docker-classic link in /usr/local/bin if you don't already have it from Docker Desktop

Building the project

$ make

This will make the cli with all backends enabled. make cross on the other hand will cross-compile the cli without the example and local backend. We use make cross to build for our release, hence the exclusion of those backends. You can still cross-compile with all backends enabled: BUILD_TAGS=example,local make cross.

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.