chk-m8

## cert-bot-aws-osx.sh
# Set-up
# Note: This will be our base path, since lets encrypt wants to use a folder inaccessible by new versions of osx
mkdir /Users/{YOUR_LOCAL_USER}/Documents/letsencrypt

# Read local certs
sudo docker run -it --rm --name certbot \
    -v "/Users/{YOUR_LOCAL_USER}/Documents/letsencrypt:/etc/letsencrypt" \
    -v "/Users/{YOUR_LOCAL_USER}/Documents/letsencrypt/lib:/var/lib/letsencrypt" \
    -p 80:80 \
    -e AWS_ACCESS_KEY_ID='{AWS_ACCESS_KEY_ID}' \

## useful_html_meta_tags.html
<head>
  <!--
    Enforce IE11 browsers to use latest renderer
    Note:
      This can be a problem when a customer uses work laptops.
      It's not limited to just being at work, but also if a customer
      tries to view your website while at work, so include this to be safe.
  -->
  <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" />
	# Set-up
	# Note: This will be our base path, since lets encrypt wants to use a folder inaccessible by new versions of osx
	mkdir /Users/{YOUR_LOCAL_USER}/Documents/letsencrypt

	# Read local certs
	sudo docker run -it --rm --name certbot \
	-v "/Users/{YOUR_LOCAL_USER}/Documents/letsencrypt:/etc/letsencrypt" \
	-v "/Users/{YOUR_LOCAL_USER}/Documents/letsencrypt/lib:/var/lib/letsencrypt" \
	-p 80:80 \
	-e AWS_ACCESS_KEY_ID='{AWS_ACCESS_KEY_ID}' \
	<head>
	<!--
	Enforce IE11 browsers to use latest renderer
	Note:
	This can be a problem when a customer uses work laptops.
	It's not limited to just being at work, but also if a customer
	tries to view your website while at work, so include this to be safe.
	-->
	<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" />