ae3a6b04fd
add logging
2020-06-02 19:07:23 +02:00
1f8ccbabb0
fixed issue with non written cert file
2020-05-16 19:32:02 +02:00
4aa0116f4d
add cache for certs to prevent hitting the rate limit
2020-05-16 19:04:13 +02:00
83019c66e1
update to debian 9
2019-06-03 09:06:27 +02:00
0a7b356df5
fix for unsupported option
2019-05-23 11:08:11 +02:00
810436a2f5
fixed minor issues
2016-12-30 10:05:42 +01:00
b3e75e564e
Fixed issues with relative directories
2016-04-12 07:29:39 +02:00
6d93f9094b
rework / refactoring / documentation
...
* rename letencrypt.conf to letsencrypt.conf
* Move more options to letsencrypt configurations file
* Done lot of rework / refactoring / documentation
2016-04-12 07:05:24 +02:00
223b49fb53
Changed actions to react on
2016-04-10 14:02:56 +02:00
b23f1297e6
Fixed wrong function call
2016-04-10 12:47:18 +02:00
c3664b34d3
first step to refactor
2016-04-10 12:36:43 +02:00
0a39d8c8b1
Add filter for containers
...
The filter will only consider containers that have domains
configured.
2016-04-10 11:54:27 +02:00
b1c32049a0
Removed unsecure RC4
...
RC4-SHA was marked insecure by https://sslanalyzer.comodoca.com
2016-04-10 09:36:03 +02:00
973abaeb23
Required Domains extracted at startup
...
The required domains are now extracted at startup of the
container via the docker socket. A certificate that contains all
domains as common or alternative name is generated and used.
2016-04-08 06:46:00 +02:00
27ba704ee6
add code to extract all resolving domains from the containers
2016-04-07 08:03:13 +02:00
a57fa08340
First semiworking iteration
...
Container can be started with empty data directory.
After using docker exec the commands from the NOTES file can be
used to create a first cert and additional certs after that.
2016-04-06 20:26:08 +02:00
