Skip to content

Commit 5158d2d

Browse files
committed
Make front page look better; Place warning in context.
1 parent 3ea65e3 commit 5158d2d

File tree

2 files changed

+5
-4
lines changed

2 files changed

+5
-4
lines changed

_posts/2015-12-17-letsencrypt-on-kubernetes.markdown

+4-4
Original file line numberDiff line numberDiff line change
@@ -9,10 +9,6 @@ tags: kubernetes
99
Below I will describe an approach as to how to get a proxy running that handles
1010
SSL termination and certificate regeneration using letsencrypt.org.
1111

12-
Please note that there are strict low quotas on the production letsencrypt
13-
endpoint,[use the --server flag][letsencrypt-staging-please] to specify the
14-
staging server during testing or face being locked out for a week.
15-
1612
## Problem
1713

1814
You've got a cat naming service, you've containerized it and it is running
@@ -124,6 +120,10 @@ your yaml env section:
124120
value: https://acme-staging.api.letsencrypt.org/directory
125121
{% endhighlight %}
126122

123+
> Please note that there are strict low quotas on the production letsencrypt
124+
endpoint, use the LETSENCRYPT_ENDPOINT env var to to specify the staging server
125+
during testing or face being locked out for a week.
126+
127127
## A letsencrypt-friendly ssl-terminating proxy
128128

129129
[ployst/nginx-ssl-proxy](https://github.com/ployst/nginx-ssl-proxy) is a fork

index.html

+1
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,7 @@ <h1 class="page-heading">Posts</h1>
1414
<h2>
1515
<a class="post-link" href="{{ post.url | prepend: site.baseurl }}">{{ post.title }}</a>
1616
</h2>
17+
{{ post.excerpt }}
1718
</li>
1819
{% endfor %}
1920
</ul>

0 commit comments

Comments
 (0)