From efcd3cf93360b92712ea25ae94be3cd3545919cb Mon Sep 17 00:00:00 2001
From: Trishank K Kuppusamy <trishank.kuppusamy@datadoghq.com>
Date: Mon, 10 Feb 2020 13:15:58 -0500
Subject: [PATCH] diff start scripts for Notary and signy

---
 scripts/{start.sh => notary-start.sh} |  2 +-
 scripts/signy-start.sh                | 18 ++++++++++++++++++
 2 files changed, 19 insertions(+), 1 deletion(-)
 rename scripts/{start.sh => notary-start.sh} (97%)
 create mode 100755 scripts/signy-start.sh

diff --git a/scripts/start.sh b/scripts/notary-start.sh
similarity index 97%
rename from scripts/start.sh
rename to scripts/notary-start.sh
index 6031151..ba74f45 100755
--- a/scripts/start.sh
+++ b/scripts/notary-start.sh
@@ -13,4 +13,4 @@ docker run -d \
   -e REGISTRY_HTTP_TLS_KEY=/certs/notary-server.key \
   registry:2
 
-docker ps
\ No newline at end of file
+docker ps
diff --git a/scripts/signy-start.sh b/scripts/signy-start.sh
new file mode 100755
index 0000000..b166956
--- /dev/null
+++ b/scripts/signy-start.sh
@@ -0,0 +1,18 @@
+#!/bin/bash 
+
+NOTARY=$GOPATH/src/github.com/theupdateframework/notary
+
+(cd $NOTARY; docker-compose up -d)
+
+# NOTE: Notary (see scripts/notary-start.sh) seems to require TLS for both the
+# Registry and itself. However, that setup breaks cnab-to-oci (required for
+# signy), most likely because we use a self-signed root here. Until we fix
+# this, it is easiest to use two different scripts to initalize the Registry
+# for Notary and signy.
+docker run -d \
+  --name registry \
+  -p 5000:5000 \
+  -e REGISTRY_HTTP_ADDR=0.0.0.0:5000 \
+  registry:2
+
+docker ps