I was asked this several times by now, and I'm still saying no.
My opinion on this is that public(!) challenge files have nothing to do right next the very private key files, they should be somewhere like /var/www and considered completely public.
@lukas2511 commented on GitHub (Dec 16, 2017):
I was asked this several times by now, and I'm still saying no.
My opinion on this is that public(!) challenge files have nothing to do right next the very private key files, they should be somewhere like /var/www and considered completely public.
I put boilerplate code in it that dispatches the challenges either true scp or gcloud app deploy acme.yaml --project $(PROJECT) it's like a extension of the hook.sh script. In case of scp i can find a work around referring to /tmp/challenges or something but in case of gcloud it gets messy to put it somewhere else
@gertcuykens commented on GitHub (Dec 17, 2017):
I put boilerplate code in it that dispatches the challenges either true `scp` or `gcloud app deploy acme.yaml --project $(PROJECT)` it's like a extension of the hook.sh script. In case of `scp` i can find a work around referring to /tmp/challenges or something but in case of gcloud it gets messy to put it somewhere else
You can add a local exclusion using .git/info/exclude, but I'm suggesting to find a way to work with a tmp directory.
@lukas2511 commented on GitHub (Dec 17, 2017):
You can add a local exclusion using `.git/info/exclude`, but I'm suggesting to find a way to work with a tmp directory.
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 @gertcuykens on GitHub (Dec 16, 2017).
Can
challenges/*be added to .gitignore please thx@lukas2511 commented on GitHub (Dec 16, 2017):
I was asked this several times by now, and I'm still saying no.
My opinion on this is that public(!) challenge files have nothing to do right next the very private key files, they should be somewhere like /var/www and considered completely public.
@gertcuykens commented on GitHub (Dec 17, 2017):
I put boilerplate code in it that dispatches the challenges either true
scporgcloud app deploy acme.yaml --project $(PROJECT)it's like a extension of the hook.sh script. In case ofscpi can find a work around referring to /tmp/challenges or something but in case of gcloud it gets messy to put it somewhere else@lukas2511 commented on GitHub (Dec 17, 2017):
You can add a local exclusion using
.git/info/exclude, but I'm suggesting to find a way to work with a tmp directory.