Originally created by @the-vindicar on GitHub (May 11, 2016).
Could this be made an option?
Or, if it can be done with hook, can you add a doc entry regarding how to do it?
Originally created by @the-vindicar on GitHub (May 11, 2016).
Could this be made an option?
Or, if it can be done with hook, can you add a doc entry regarding how to do it?
I don't want any more formats of keys and certs so this would have to be done with a hook script.
In theory something like this should work (untested):
#!/usr/bin/env bash
function deploy_cert {
local DOMAIN="${1}" KEYFILE="${2}" CERTFILE="${3}" FULLCHAINFILE="${4}" CHAINFILE="${5}" TIMESTAMP="${6}"
cat "${KEYFILE}" "${FULLCHAINFILE}" > "${BASEDIR}/certs/${DOMAIN}/combined.pem"
}
@lukas2511 commented on GitHub (May 11, 2016):
I don't want any more formats of keys and certs so this would have to be done with a hook script.
In theory something like this should work (untested):
```
#!/usr/bin/env bash
function deploy_cert {
local DOMAIN="${1}" KEYFILE="${2}" CERTFILE="${3}" FULLCHAINFILE="${4}" CHAINFILE="${5}" TIMESTAMP="${6}"
cat "${KEYFILE}" "${FULLCHAINFILE}" > "${BASEDIR}/certs/${DOMAIN}/combined.pem"
}
```
Ah, no, no... Lighttpd has 2 config options ssl.pemfile and ssl.ca-file. Former should contain both KEYFILE and CERTFILE, latter is FULLCHAINFILE.
@domenpk commented on GitHub (Jun 8, 2016):
Ah, no, no... Lighttpd has 2 config options `ssl.pemfile` and `ssl.ca-file`. Former should contain both KEYFILE and CERTFILE, latter is FULLCHAINFILE.
Interesting... don't even want to know how it came to this.
Anyway, with hooks this can easily be done :)
@lukas2511 commented on GitHub (Jun 8, 2016):
Interesting... don't even want to know how it came to this.
Anyway, with hooks this can easily be done :)
Using the hook method now and it works fine, thanks!
However, you might still want to add this use-case to documentation, for googlers' sake.
@the-vindicar commented on GitHub (Jun 8, 2016):
Using the hook method now and it works fine, thanks!
However, you might still want to add this use-case to documentation, for googlers' sake.
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 @the-vindicar on GitHub (May 11, 2016).
Could this be made an option?
Or, if it can be done with hook, can you add a doc entry regarding how to do it?
@lukas2511 commented on GitHub (May 11, 2016):
I don't want any more formats of keys and certs so this would have to be done with a hook script.
In theory something like this should work (untested):
@domenpk commented on GitHub (Jun 8, 2016):
Hook should actually contain CERTFILE instead of FULLCHAINFILE:
@lukas2511 commented on GitHub (Jun 8, 2016):
@domenpk and then you are missing the chain certificates, which are important too ¯(ツ)/¯
@domenpk commented on GitHub (Jun 8, 2016):
Ah, no, no... Lighttpd has 2 config options
ssl.pemfileandssl.ca-file. Former should contain both KEYFILE and CERTFILE, latter is FULLCHAINFILE.@lukas2511 commented on GitHub (Jun 8, 2016):
Interesting... don't even want to know how it came to this.
Anyway, with hooks this can easily be done :)
@the-vindicar commented on GitHub (Jun 8, 2016):
Using the hook method now and it works fine, thanks!
However, you might still want to add this use-case to documentation, for googlers' sake.