Fix #16 by specifying VENV_PATH when running letsencrypt. #17
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
However, puppet exec's will not set $HOME, which will stop Debian's
/bin/sh, dash, from expanding
, so it creates a literal '' folder.