Go to file

Jan Christian Grünhage f4eb210180 All checks were successful the build was successful Details chore(ci): add initial ci config		2017-12-06 14:09:50 +01:00
root/etc	Added missing quotation marks, configured dehydrated to run once to register initially	2017-12-01 17:32:19 +01:00
.drone.yml	chore(ci): add initial ci config	2017-12-06 14:09:50 +01:00
Dockerfile	Refactor config-modification into a service, document the optional environment variables so not setting them will not modify the configuration file, introduce check to see if config file exists before blindly copying one	2017-12-01 09:28:36 +01:00
README.md	Linked Zero-Config-Tutorial in README, improved wording a bit on the tutorial	2017-12-06 08:32:35 +01:00
zero-config-mode.md	Linked Zero-Config-Tutorial in README, improved wording a bit on the tutorial	2017-12-06 08:32:35 +01:00

README.md

docker-dehydrated

This is a docker container that wraps around dehydrated.

Usage

For a short tutorial on how to use this container with zero-configuration to sign certificates using the HTTP-Challenge, see zero-config-mode.md.

Environment variables

The following environment variables can be set to influence the container's behaviour:

$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 into /etc/dehydrated/config.