Originally created by @leeps on GitHub (Mar 20, 2017).
dehydrated creates symlinks to the current PEM-encoded certificate files. These are named
cert.pem (and cert.csr) for the certificate (resp. the CSR)
chain.pem for the intermediary certifcate, which the server needs to send too
fullchain.pem for the concatenation of the above two
privkey.pem for the file containing the private key
Please make the names of these links configurable. It would help with integration where not all certificates are managed by dehydrated.
Originally created by @leeps on GitHub (Mar 20, 2017).
dehydrated creates symlinks to the current PEM-encoded certificate files. These are named
- `cert.pem` (and `cert.csr`) for the certificate (resp. the CSR)
- `chain.pem` for the intermediary certifcate, which the server needs to send too
- `fullchain.pem` for the concatenation of the above two
- `privkey.pem` for the file containing the private key
Please make the names of these links configurable. It would help with integration where not all certificates are managed by dehydrated.
For integration you can use a deploy_cert hook, this hook is exactly intended for that purpose. Just write a simple script that copies the certificates to where you want them.
@lukas2511 commented on GitHub (Jul 10, 2017):
For integration you can use a `deploy_cert` hook, this hook is exactly intended for that purpose. Just write a simple script that copies the certificates to where you want them.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @leeps on GitHub (Mar 20, 2017).
dehydrated creates symlinks to the current PEM-encoded certificate files. These are named
cert.pem(andcert.csr) for the certificate (resp. the CSR)chain.pemfor the intermediary certifcate, which the server needs to send toofullchain.pemfor the concatenation of the above twoprivkey.pemfor the file containing the private keyPlease make the names of these links configurable. It would help with integration where not all certificates are managed by dehydrated.
@lukas2511 commented on GitHub (Jul 10, 2017):
For integration you can use a
deploy_certhook, this hook is exactly intended for that purpose. Just write a simple script that copies the certificates to where you want them.