Skip to content

Commit 2b4c966

Browse files
committed
Updates for the 0.2 release.
All Dockerfile instructions are now supported.
1 parent 557e494 commit 2b4c966

5 files changed

Lines changed: 518 additions & 15 deletions

File tree

Cargo.lock

Lines changed: 1 addition & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

Cargo.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
[package]
22
name = "dockerfile"
33
description = "A Rust library for dynamically generating Dockerfiles."
4-
version = "0.1.1"
4+
version = "0.2.0"
55

66
authors = ["Anthony Dodd <dodd.anthonyjosiah@gmail.com>"]
77
categories = ["api-bindings", "config", "data-structures", "development-tools"]

README.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,8 @@ A Rust library for dynamically generating Dockerfiles.
1313

1414
The use case this crate was originally built for was to build Docker images from a worker service running in Kubernetes for client workloads. This is definitely not the only pattern that is supported. The generated Dockerfiles could be persisted somewhere or discarded immediately after use. The containers generated are standard containers, built according to the Dockerfiles you generated.
1515

16+
All of the Dockerfile instructions are supported in raw form as of 2018.12.09. There is an issue open to add more structured and type-safe interfaces for the instructions which need it.
17+
1618
### get started
1719
First you will need to add this to your `Cargo.toml` dependencies.
1820

@@ -50,4 +52,4 @@ CMD echo 'Hello. Goodbye.'
5052
```
5153

5254
### development
53-
This crate is in an early state, and there are a few additional things to be done with it. I would like to experiment with adding constructors for the various forms of instructions; EG, offer a constructor for `CMD` which takes an `impl Iterator<Item=AsRef<str>>` for building the form `CMD ["arg0", "arg1"]` &c. Not sure on that yet.
55+
I would like to have this crate offer a type-safe interface for constructing the various Dockerfile instructions. This will help reduce bugs which could only be found once you actually attempt to invoke the docker build. I would like to experiment with adding constructors for the various forms of instructions; EG, offer a constructor for `CMD` which takes an `impl Iterator<Item=AsRef<str>>` for building the form `CMD ["arg0", "arg1"]` &c.

0 commit comments

Comments
 (0)