From ed3b984ea5a35fa88816914414e679eb26c94f88 Mon Sep 17 00:00:00 2001
From: Pascal Vizeli <pascal.vizeli@syshack.ch>
Date: Sat, 22 Apr 2017 23:54:57 +0200
Subject: [PATCH] update description

---
 README.md               | 8 +++++++-
 letsencrypt/config.json | 2 +-
 smb_config/config.json  | 1 -
 3 files changed, 8 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 1eba850..f9818eb 100644
--- a/README.md
+++ b/README.md
@@ -20,6 +20,8 @@ Use `FROM %%BASE_IMAGE%%` inside your docker file. We use alpine linux 3.5 for a
 ENV VERSION %%VERSION%%
 ```
 
+You should use bash scripts for simple stuff inside docker to hold the image small.
+
 ## Addon config
 
 ```json
@@ -42,7 +44,7 @@ ENV VERSION %%VERSION%%
     "list1": [
       "str|int|float|bool|email|url"
     ],
-    "list2": [
+   "list2": [
       { "ble": "str|int|float|bool|email|url" }
     ]
   },
@@ -52,5 +54,9 @@ ENV VERSION %%VERSION%%
 
 If you want to set a value to requered and need to be set from user before it start the addon, set it to null.
 
+## SSL
+
+Default you can use `fullchain.pem` and `privkey.pem` from `/ssl` for you stuff. Your SSL addon should also create default this files.
+
 ## Addon need to known
 `/data` is a volume with a persistant store. `/data/options.json` have the user config inside. You can use `jq` inside shell script to parse this data. A other nice tool for write plugin is [Supervisor](http://supervisord.org/).
diff --git a/letsencrypt/config.json b/letsencrypt/config.json
index 4b28dac..3fe6bea 100644
--- a/letsencrypt/config.json
+++ b/letsencrypt/config.json
@@ -13,7 +13,7 @@
     "email": null,
     "domains": [null],
     "certfile": "fullchain.pem",
-    "keyfile": "keyfile.pem"
+    "keyfile": "privkey.pem"
   },
   "schema": {
     "email": "email",
diff --git a/smb_config/config.json b/smb_config/config.json
index b42dbe1..c446be8 100644
--- a/smb_config/config.json
+++ b/smb_config/config.json
@@ -9,7 +9,6 @@
     "445/tcp": 445
    },
   "map_config": true,
-  "map_ssl": false,
   "options": {
       "workgroup": "WORKGROUP",
       "guest": true,