Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closes #18: merging @mheistermann's changes #32

Merged
merged 6 commits into from
Apr 28, 2016
Merged

Conversation

danzilio
Copy link
Member

No description provided.

mheistermann and others added 6 commits March 3, 2016 18:10
Issue copy-paste from
#16

When you install letsencrypt using the VCS method, it will create a
virtualenv, which would normally be located in
~/.local/share/letsencrypt:

Excerpt from letsencrypt-auto:
```
XDG_DATA_HOME=${XDG_DATA_HOME:-~/.local/share}
VENV_NAME="letsencrypt"
VENV_PATH=${VENV_PATH:-"$XDG_DATA_HOME/$VENV_NAME"}
```
However, puppet exec's will not set $HOME, which will stop Debian's
/bin/sh, dash, from expanding ~, so it creates a literal '~' folder.
Using the `cron_success_command` parameter for `certonly`, you can
run commands when the renewal command was successful, e.g.
reload the webserver to use the renewed certs.

Not sure about letsencrypt return values, so the command might be
executed even if the cert is unchanged, doesn't matter for this
usecase though.
… into cron_success_cmd

Conflicts:
	manifests/certonly.pp
	manifests/init.pp
	manifests/params.pp
@danzilio danzilio merged commit 547a4ea into master Apr 28, 2016
@danzilio danzilio deleted the cron_success_cmd branch April 28, 2016 13:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants