grim/convey

Another typo fix

2018-01-14, Gary Kramlich
309efdf0a7b1
Parents 4022dd81834e
Children 55357dedb9f4
Another typo fix
1 files changed, 1 insertions(+), 1 deletions(-)
  • +1 -1
    README.md
    • --- a/README.md Sun Jan 14 20:30:51 2018 -0600
    +++ b/README.md Sun Jan 14 20:31:34 2018 -0600
    @@ -26,7 +26,7 @@
    # Concepts
    -Convey is build around a concept that I call a build container. A build container is a container that has all of the dependencies to turn an input into something else. This could be source code or even just data processing. For example the `convey/go-build` image is a simple wrapper around the `golang` image that just builds a project instead of installing it. You can find more information on build containers [here](http://blog.terranillius.com/post/docker_builder_pattern/).
    +Convey is built around a concept that I call a build container. A build container is a container that has all of the dependencies to turn an input into something else. This could be source code or even just data processing. For example the `convey/go-build` image is a simple wrapper around the `golang` image that just builds a project instead of installing it. You can find more information on build containers [here](http://blog.terranillius.com/post/docker_builder_pattern/).
    Convey is built around this concept to allow you to build/process anything on any platform while at the same time protecting the host from a malicious config. This protection is provided by not exposing dangerous options like volume mounts or port forwards while running containers. This is accomplished by creating a volume a data volume at the start of the build plan and volume mounting it into containers as they are run. This allows you to pass state between modular tasks that can be reused between multiple plans.