From 2ee6ac70b8b141400b8f0b686f82a4bee3ee9ea4 Mon Sep 17 00:00:00 2001
From: Michele Locati <michele@locati.it>
Date: Tue, 21 Jan 2020 09:25:04 +0100
Subject: [PATCH] Let users use cached Docker images

---
 Dockerfile | 17 +++++++++++++++++
 README.md  | 17 +++++++++++++++++
 2 files changed, 34 insertions(+)
 create mode 100644 Dockerfile

diff --git a/Dockerfile b/Dockerfile
new file mode 100644
index 0000000..00ba3d9
--- /dev/null
+++ b/Dockerfile
@@ -0,0 +1,17 @@
+FROM bash AS build
+
+COPY c5 /tmp/
+COPY c5.bat /tmp/
+COPY composerpkg /tmp/
+COPY composerpkg.bat /tmp/
+
+RUN \
+    chmod 0755 /tmp/c5 /tmp/composerpkg && \
+    chmod 0555 /tmp/c5.bat /tmp/composerpkg.bat
+
+FROM scratch
+
+COPY --from=build /tmp/c5 /usr/bin/
+COPY --from=build /tmp/composerpkg /usr/bin/
+COPY --from=build /tmp/c5.bat /usr/bin/
+COPY --from=build /tmp/composerpkg.bat /usr/bin/
diff --git a/README.md b/README.md
index 0ee8aa0..4b4fe3c 100644
--- a/README.md
+++ b/README.md
@@ -85,3 +85,20 @@ That leads to having to having two running copies of the same library (one in th
 
 To avoid these problems, you can run the `composerpkg` command included in this repository (for Windows users, you'll also need the `composerpkg.bat` file - to be saved in the same directory as the `composerpkg` file).
 `composerpkg` accepts the same arguments accepted by the plain `composer` command, but when you install/update the dependencies, you won't have duplicated stuff in your vendor directory.
+
+
+## Using the scripts in Docker images
+
+You can download the scripts on the fly, like this:
+
+```Dockerfile
+ADD https://raw.githubusercontent.com/concrete5/cli/master/c5 /usr/bin/
+
+RUN chmod +x /usr/bin/c5
+```
+
+You can also copy them from a Docker image, so that your build process doesn't have to download the scripts every time you need them:
+
+```Dockerfile
+COPY --from=concrete5/cli /usr/bin/c5 /usr/bin/
+```