2017-12-01 10:29:31 +00:00
|
|
|
# docker-dehydrated
|
2017-12-01 08:28:36 +00:00
|
|
|
|
2017-12-06 13:27:29 +00:00
|
|
|
[![Build Status](https://drone.jcg.re/api/badges/jcgruenhage/tex-docs/status.svg)](https://drone.jcg.re/jcgruenhage/docker-dehydrated)
|
|
|
|
|
2017-12-01 08:28:36 +00:00
|
|
|
This is a docker container that wraps around [dehydrated](https://github.com/lukas2511/dehydrated).
|
|
|
|
|
2017-12-06 07:32:35 +00:00
|
|
|
## Usage
|
|
|
|
|
|
|
|
For a short tutorial on how to use this container with zero-configuration to sign certificates
|
2017-12-06 13:32:43 +00:00
|
|
|
using the HTTP-Challenge, see ["Zero-Config"-Mode"](zero-config-mode.md).
|
2017-12-06 07:32:35 +00:00
|
|
|
|
2017-12-01 08:28:36 +00:00
|
|
|
## Environment variables
|
|
|
|
|
|
|
|
The following environment variables can be set to influence the container's behaviour:
|
|
|
|
|
2017-12-01 10:29:31 +00:00
|
|
|
- `$ENDPOINT` which ACME-Endpoint you want to use, supported values: "staging", "production" (default).
|
|
|
|
- `$CHALLENGE` what type of challenge should be used, supported values: "http-01" (default), "dns-01"
|
|
|
|
|
|
|
|
If the environment variables were not explicitely set, no modification to the configuration file is made
|
|
|
|
|
|
|
|
## Behaviour on startup
|
|
|
|
|
|
|
|
When the container is started, a script is run which looks for the configuration file in the places supported by dehydrated,
|
|
|
|
and if no configuration file is found, it will copy the [example configuration file](https://github.com/lukas2511/dehydrated/docs/examples/config)
|
|
|
|
into `/etc/dehydrated/config`.
|
2017-12-06 07:32:35 +00:00
|
|
|
|