From 5e10df8e5a1b455ed57cc69b8f2786ad119987de Mon Sep 17 00:00:00 2001 From: Phil Kunz Date: Sat, 18 Jun 2016 16:14:57 +0200 Subject: [PATCH] update REAMDE --- README.md | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index b218540..14df2d0 100644 --- a/README.md +++ b/README.md @@ -12,11 +12,20 @@ let myCert = new Cert({ cfEmail: "some@cloudflare.email", cfKey: "someCloudflareApiKey", sslDir: "someOutputPath", // NOTE: if you already have certificates, make sure you put them in here, so cert only requires the missing ones - gitOriginRepo: "git@githhub.com/someuser/somereopo" // good for pesistence in highly volatile environments like docker + gitOriginRepo: "git@githhub.com/someuser/somereopo" // good for persistence in highly volatile environments like docker }); myCert.getDomainCert("example.com"); ``` ### sslDir -to use the certificates it is important to understand what the structure of the ssl directory looks like. \ No newline at end of file +to use the certificates it is important to understand what the structure of the ssl directory looks like. + +### using a git origin repo. +Often times you want to keep track of certificates in order to keep them +even if the point of initial certificate request is gone. Imagine you have a dockerenvironement +and you keep starting new container versions for the same domain. YOu ideally want to use a proxy +that handles SSL managemet for you. But even the proxy needs to be updated from time to time. + +So you need some kind of persistence between versions. This is why you can sync up all certificates to a git repo over ssh +Just make sure your id_rsa is in place for the node user and is allowed for the origin repo. \ No newline at end of file