moving lets encrypt to its own doc

README.md

@@ -103,19 +103,8 @@ Sometimes you need a custom config file for nginx to do rewrites or password pro
 There is often an occasion where you need to run a script on code to do a transformation once code lands in the container. For this reason we have developed scripting support. By including a scripts folder in your git repository and passing the __RUN_SCRIPTS=1__ flag to your command line the container will execute your scripts. Please see the [repo layout guidelines](https://github.com/ngineered/nginx-php-fpm/blob/master/docs/repo_layout.md) for more details on how to organise this.
 
 ### Lets Encrypt support
-#### Enabling SSL or Special Nginx Configs
-You can either map a local folder containing your configs to /etc/nginx or (recommended method) edit the files within the  __conf__ directory in a copy of this git repo, and then rebuilding the base image.
-#### Setup
-You can use Lets Encrypt to secure your container. Make sure you start the container with the ```DOMAIN, GIT_EMAIL``` and ```WEBROOT``` variables set to enable this functionality. Then run:
-```
-sudo docker exec -t <CONTAINER_NAME> /usr/bin/letsencrypt-setup
-```
-Ensure your container is accessible on the ```DOMAIN``` you supplied in order for this to work
-#### Renewal
-Lets Encrypt certs expire every 90 days, to renew simply run:
-```
-sudo docker exec -t <CONTAINER_NAME> /usr/bin/letsencrypt-renew
-```
+[Lets Encrypt Guide](https://github.com/ngineered/nginx-php-fpm/blob/master/docs/lets_encrypt.md)
+
 ## Special Git Features
 Specify the ```GIT_EMAIL``` and ```GIT_NAME``` variables for this to work. They are used to set up git correctly and allow the following commands to work.