readme: mores infos about WELLKNOWN

README.md

@@ -49,18 +49,34 @@ example.net www.example.net wiki.example.net
 This states that there should be two certificates `example.com` and `example.net`,
 with the other domains in the corresponding line being their alternative names.
 
-### example nginx config
+### $WELLKNOWN / challenge-response
 
-If you want to use nginx you can set up a location block to serve your challenge responses:
+Boulder (acme-server) is looking for challenge responses under your domain in the `.well-known/acme-challenge` directory
 
+This script uses `http-01`-type verification (for now) so you need to have the that directory available over normal http (no ssl).
+
+A full URL would look like `http://example.org/.well-known/acme-challenge/c3VjaC1jaGFsbGVuZ2UtbXVjaA-aW52YWxpZC13b3c`.
+
+An example setup to get this to work would be:
+
+nginx.conf:
 ```
+...
 location /.well-known/acme-challenge {
-  root /var/www/letsencrypt;
+  alias /var/www/letsencrypt;
 }
+...
 ```
 
-For this to work i'd suggest either configuring `/var/www/letsencrypt` as WELLKNOWN directory,
-or to create a symlink to the default location next to the script: `ln -s /var/www/letsencrypt .acme-challenges`
+config.sh:
+```bash
+...
+WELLKNOWN="/var/www/letsencrypt"
+...
+```
+
+An alternative to setting the WELLKNOWN variable would be to create a symlink to the default location next to the script (or BASEDIR):
+`ln -s /var/www/letsencrypt .acme-challenges`
 
 ## Import