Skip to content

Commit

Permalink
Release v0.3.0
Browse files Browse the repository at this point in the history
  • Loading branch information
janeczku committed May 31, 2016
1 parent 4627704 commit f8965f6
Show file tree
Hide file tree
Showing 4 changed files with 25 additions and 15 deletions.
4 changes: 2 additions & 2 deletions Dockerfile
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
FROM alpine:3.3
MAINTAINER Jan Broer <jan@festplatte.eu.org>
MAINTAINER <jan@rancher.com>

RUN apk add --no-cache ca-certificates

ENV LETSENCRYPT_RELEASE v0.2.9
ENV LETSENCRYPT_RELEASE v0.3.0

ADD https://github.com/janeczku/rancher-letsencrypt/releases/download/${LETSENCRYPT_RELEASE}/rancher-letsencrypt-linux-amd64.tar.gz /tmp/rancher-letsencrypt.tar.gz

Expand Down
12 changes: 11 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,17 @@ A [Rancher](http://rancher.com/rancher/) service that obtains free SSL/TLS certi
This application is distributed via the [Rancher Community Catalog](https://github.com/rancher/community-catalog).

Enable the Community Catalog under `Admin` => `Settings` in the Rancher UI.
Then find the `Let's Encrypt` template in the Catalog section of the UI and follow the instructions.
Then locate the `Let's Encrypt` template in the Catalog section of the UI and follow the instructions.

#### Accessing certificates and private keys from other services
The created SSL certificate is stored in Rancher for usage in load balancers.
If you want to use it from other services (e.g. a Nginx container) you can opt to save the certificate and private key to a host path,
named volume or Convoy storage volume. You can then mount the volume or host path to other containers and access the files as follows:
`<path_on_host or volume name>/<certificate name>/fullchain.pem`
`<path_on_host or volume name>/<certificate name>/privkey.pem`
where `<certificate name>` is the name you specified in the UI forced to this set of characters: `[a-zA-Z0-9-_.]`.



### Provider specific usage

Expand Down
2 changes: 1 addition & 1 deletion VERSION
Original file line number Diff line number Diff line change
@@ -1 +1 @@
v0.2.9
v0.3.0
22 changes: 11 additions & 11 deletions context.go
Original file line number Diff line number Diff line change
Expand Up @@ -71,17 +71,17 @@ func (c *Context) InitContext() {
}

providerOpts := letsencrypt.ProviderOpts{
Provider: letsencrypt.DnsProvider(providerParam),
CloudflareEmail: getEnvOption("CLOUDFLARE_EMAIL", false),
CloudflareKey: getEnvOption("CLOUDFLARE_KEY", false),
DoAccessToken: getEnvOption("DO_ACCESS_TOKEN", false),
AwsAccessKey: getEnvOption("AWS_ACCESS_KEY", false),
AwsSecretKey: getEnvOption("AWS_SECRET_KEY", false),
DNSimpleEmail: getEnvOption("DNSIMPLE_EMAIL", false),
DNSimpleKey: getEnvOption("DNSIMPLE_KEY", false),
DynCustomerName: getEnvOption("DYN_CUSTOMER_NAME", false),
DynUserName: getEnvOption("DYN_USER_NAME", false),
DynPassword: getEnvOption("DYN_PASSWORD", false),
Provider: letsencrypt.DnsProvider(providerParam),
CloudflareEmail: getEnvOption("CLOUDFLARE_EMAIL", false),
CloudflareKey: getEnvOption("CLOUDFLARE_KEY", false),
DoAccessToken: getEnvOption("DO_ACCESS_TOKEN", false),
AwsAccessKey: getEnvOption("AWS_ACCESS_KEY", false),
AwsSecretKey: getEnvOption("AWS_SECRET_KEY", false),
DNSimpleEmail: getEnvOption("DNSIMPLE_EMAIL", false),
DNSimpleKey: getEnvOption("DNSIMPLE_KEY", false),
DynCustomerName: getEnvOption("DYN_CUSTOMER_NAME", false),
DynUserName: getEnvOption("DYN_USER_NAME", false),
DynPassword: getEnvOption("DYN_PASSWORD", false),
}

c.Acme, err = letsencrypt.NewClient(emailParam, keyType, apiVersion, providerOpts)
Expand Down

0 comments on commit f8965f6

Please sign in to comment.