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

Store user settings seperately from letsencrypt.exe.config for xcopy upgrades #720

Closed
ghost opened this issue Jan 26, 2018 · 3 comments
Closed

Comments

@ghost
Copy link

ghost commented Jan 26, 2018

I want LEWS to be able to parse it's letsencrypt.exe.config file from a different path specified in a environment variable. Doing this will allow me and Scoop users to persist configuration changes across upgrades of LEWS via Scoop.

See my commit: ScoopInstaller/Scoop@7122c4f

@WouterTinus
Copy link
Member

I see where you want to go with this - and I think it might even be possible - but it would have to be a bit more elaborate than merely reading letsencrypt.exe.config from a different location. This kind of .config file in the .NET world also serves the purpose of initializing the CLR with the correct assembly redirects etc., so that stuff would have to be separated from the user settings in order to ensure successful upgrades.

Thanks for including LEWS into your project by the way, I wasn't familiar with it before but it seems useful!

@WouterTinus WouterTinus changed the title Parse letsencrypt.exe.config file from an environment variable Store user settings seperately from letsencrypt.exe.config for xcopy upgrades Jan 27, 2018
@ghost ghost closed this as completed Jan 29, 2018
@WouterTinus WouterTinus reopened this Jan 30, 2018
@WouterTinus
Copy link
Member

Reopening because it would make sense to do this.

WouterTinus added a commit that referenced this issue Feb 12, 2018
@WouterTinus
Copy link
Member

This is done by the new release!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant