You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-12Lines changed: 4 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,24 +44,16 @@ The Drycc project welcomes contributions from all developers. The high level pro
44
44
* If your PR fixes any [issues][issues], make sure you write `Fixes #1234` in your PR description (where `#1234` is the number of the issue you're closing)
45
45
* The Drycc core contributors will review your code. After each of them sign off on your code, they'll label your PR with `LGTM1` and `LGTM2` (respectively). Once that happens, a contributor will merge it
46
46
47
-
## Docker Based Development Environment
47
+
## Container Based Development Environment
48
48
49
-
The preferred environment for development uses [the `go-dev`Docker image](https://github.com/drycc/docker-go-dev). The tools described in this section are used to build, test, package and release each version of Drycc.
49
+
The preferred environment for development uses [the `go-dev`Container image](https://github.com/drycc/go-dev). The tools described in this section are used to build, test, package and release each version of Drycc.
50
50
51
-
To use it yourself, you must have [make](https://www.gnu.org/software/make/) installed and Docker installed and running on your local development machine.
51
+
To use it yourself, you must have [make](https://www.gnu.org/software/make/) installed and Container installed and running on your local development machine.
52
52
53
-
If you don't have Docker installed, please go to https://www.docker.com/ to install it.
53
+
If you don't have Podman installed, please go to https://podman.io/ to install it.
54
54
55
55
After you have those dependencies, grab Go dependencies with `make bootstrap`, build your code with `make build` and execute unit tests with `make test`.
56
56
57
-
## Native Go Development Environment
58
-
59
-
You can also use the standard `go` toolchain to build and test if you prefer. To do so, you'll need [glide](https://github.com/Masterminds/glide) 0.9 or above and [Go 1.6](http://golang.org) or above installed.
60
-
61
-
After you have those dependencies, you can build and unit-test your code with `go build` and `go test $(glide nv)`, respectively.
62
-
63
-
Note that you will not be able to build or push Docker images using this method of development.
64
-
65
57
# Testing
66
58
67
59
The Drycc project requires that as much code as possible is unit tested, but the core contributors also recognize that some code must be tested at a higher level (functional or integration tests, for example).
0 commit comments