|
|
@@ -19,13 +19,13 @@ a single file, all images are expected to be created under a different tag.
|
|
|
### Instruction format
|
|
|
|
|
|
Each line represents a build instruction.
|
|
|
-There are different formats that `stackbrew` is able to parse.
|
|
|
+There are different formats that Stackbrew is able to parse.
|
|
|
|
|
|
<git-url>
|
|
|
git://github.com/dotcloud/hipache
|
|
|
https://github.com/dotcloud/docker.git
|
|
|
|
|
|
-The simplest format. `stackbrew` will fetch data from the provided git
|
|
|
+The simplest format. Stackbrew will fetch data from the provided git
|
|
|
repository from the `HEAD`of its `master` branch. Generated image will be
|
|
|
tagged as `latest`. Use of this format is discouraged because there is no
|
|
|
way to ensure stability.
|
|
|
@@ -34,7 +34,7 @@ way to ensure stability.
|
|
|
bleeding-edge git://github.com/dotcloud/docker
|
|
|
unstable https://github.com/dotcloud/docker-redis.git
|
|
|
|
|
|
-A more advanced format. `docker-brew` will fetch data from the provided git
|
|
|
+A more advanced format. Stackbrew will fetch data from the provided git
|
|
|
repository from the `HEAD`of its `master` branch. Generated image will be
|
|
|
tagged as `<docker-tag>`. Recommended if we always want to provide a snapshot
|
|
|
of the latest development. Again, no way to ensure stability.
|
|
|
@@ -46,8 +46,8 @@ of the latest development. Again, no way to ensure stability.
|
|
|
<docker-tag> <git-url> C:<git-commit-id>
|
|
|
2.2.0 git://github.com/dotcloud/docker-redis C:a4bf8923ee4ec566d3ddc212
|
|
|
|
|
|
-The most complete format. `docker-brew` will fetch data from the provided git
|
|
|
-repository from the provided reference (if it's a branch, brew will fetch its
|
|
|
+The most complete format. Stackbrew will fetch data from the provided git
|
|
|
+repository from the provided reference (if it's a branch, Stackbrew will fetch its
|
|
|
`HEAD`). Generated image will be tagged as `<docker-tag>`. Recommended whenever
|
|
|
possible.
|
|
|
|
shin-