Luke Hamburg

I'm confused, sorry. I want my `--deploy-hook` script to execute ONCE only upon a NEW cert being obtained. Is method A, B, or C below correct? ### Method A 1)...

Ok thanks @mohag Just to clarify, even when specifying the `--deploy-hook` commandline argument, the resulting config file ends up containing a line that reads `renew_hook = ...` ?

Thanks again. For future reference, I found [this post][1] from the LE/certbot forums to be very clear and helpful as well. [1]: https://community.letsencrypt.org/t/renewal-hooks-per-domain/175621/3

I looked into this a bit since I'm the original author of that portion of the workflow. Seems it's in need of some dusting off! I've just posted updated versions...

@blacs30 While we wait for @torbenkeller to test, I've submitted these changes as PR https://github.com/blacs30/bitwarden-alfred-workflow/pull/176

The workflow should be automatically making those scripts +x executable, but I'll need to check on that. For now, try opening a Terminal and pasting ``` cd '/Users/torben/Library/Application Support/Alfred/Alfred.alfredpreferences/workflows/user.workflow.DA388574-13BA-4CE9-9B0C-D96C84AE7AC0' chmod...

I just pushed another update to #176 with an auto-fix for the `+x` flag. If that gets merged it could help with this

@blacs30 I am happy to help, but I'm a bit uneasy about pushing a new release before reviewing the steps with you, becauce I think it involves compiling the `bitwarden-alfred-workflow`...

Thanks @wollew you're right. It wasn't technically a typo, but rather a missed instance of that bwexec variable which got renamed somewhere along the way. Good catch and sorry for...

@tophee It should look like this