summaryrefslogtreecommitdiff
path: root/complement
diff options
context:
space:
mode:
authorJonathan de Jong <jonathan@automatia.nl>2023-01-26 18:28:33 +0100
committerJonathan de Jong <jonathan@automatia.nl>2023-01-26 18:28:33 +0100
commite13dc7c14a0c5b318a57e47b37fddd92203d32a6 (patch)
treee5383c6cb214e2de172f5c5599dd30356a1d5154 /complement
parentb158896396bf33e088dd35ec651c52e6afe646e5 (diff)
downloadconduit-e13dc7c14a0c5b318a57e47b37fddd92203d32a6.zip
add little readme
Diffstat (limited to 'complement')
-rw-r--r--complement/README.md13
1 files changed, 13 insertions, 0 deletions
diff --git a/complement/README.md b/complement/README.md
new file mode 100644
index 0000000..b86aab3
--- /dev/null
+++ b/complement/README.md
@@ -0,0 +1,13 @@
+# Running Conduit on Complement
+
+This assumes that you're familiar with complement, if not, please readme
+[their readme](https://github.com/matrix-org/complement#running).
+
+Complement works with "base images", this directory (and Dockerfile) helps build the conduit complement-ready docker
+image.
+
+To build, `cd` to the base directory of the workspace, and run this:
+
+`docker build -t complement-conduit:dev -f complement/Dockerfile .`
+
+Then use `complement-conduit:dev` as a base image for running complement tests.