vcs-installed letsencrypt-auto creates '~' directory #16
Comments
mheistermann
added a commit
to mheistermann/puppet-letsencrypt
that referenced
this issue
Feb 25, 2016
Issue copy-paste from voxpupuli#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.
This was referenced Feb 25, 2016
mheistermann
added a commit
to mheistermann/puppet-letsencrypt
that referenced
this issue
Feb 25, 2016
Issue copy-paste from voxpupuli#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.
mheistermann
added a commit
to mheistermann/puppet-letsencrypt
that referenced
this issue
Mar 3, 2016
Issue copy-paste from voxpupuli#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.
danzilio
added a commit
that referenced
this issue
Mar 11, 2016
Fix #16 by specifying VENV_PATH when running letsencrypt.
cegeka-jenkins
pushed a commit
to cegeka/puppet-letsencrypt
that referenced
this issue
Oct 23, 2017
Issue copy-paste from voxpupuli#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.
cegeka-jenkins
pushed a commit
to cegeka/puppet-letsencrypt
that referenced
this issue
Oct 23, 2017
Issue copy-paste from voxpupuli#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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.I'm currently fixing this, will create a pull request soon.
The text was updated successfully, but these errors were encountered: