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

Ignoring %appdata% or %userprofile% changes prior to launch #354

Closed
gordonfpanam opened this issue Feb 9, 2017 · 1 comment
Closed

Ignoring %appdata% or %userprofile% changes prior to launch #354

gordonfpanam opened this issue Feb 9, 2017 · 1 comment

Comments

@gordonfpanam
Copy link

In an attempt to work around #146 I tried changing the environment variables %appdata% and %userprofile% in a separate CMD session before running letsencrypt.exe. It's just a simple:

set appdata=%allusersprofile%

...which would change this for that session only to point somewhere else. If I do this for %appdata% neither the displayed config folder or cert folder change. If I instead change where %userprofile% points then the leading components are omitted and the folders reference the current folder instead.

I could live with it referencing the current folder I suppose, but that's not how I figured this was using the environment variables. Normally one doesn't go mucking about with system-defined environment variables, but after checking that these are set per process (or per CMD session) only, I figured it wouldn't hurt to try on my test server.

I do see a fork that supports changing the config folder in .config but that hasn't been merged here.

@nul800sebastiaan
Copy link
Contributor

This will be fixed in v2 with the --configpath parameter. See PR: #394

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

No branches or pull requests

2 participants