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

Unattended Runs for All Plugins #151

Closed
rkerber opened this Issue Feb 24, 2016 · 8 comments

Comments

Projects
None yet
3 participants
@rkerber
Collaborator

rkerber commented Feb 24, 2016

So a few people have requested the ability to have more unattended runs of the client.

I have been thinking about changing it so the existing manualhost and webroot arguments work for any plugin (FTP & WebDav require you to enter a secure string for your password so they might not work right away) and you just have to tell it what plugin to use in addition to manualhost and webroot.

Does anyone else think that it should allow for more unattended uses?

@rkerber

This comment has been minimized.

Collaborator

rkerber commented Apr 10, 2016

If anyone wants to see this enhancement, add your +1 (via add your reaction) to the first comment of this issue.

@sthammadi-spsc

This comment has been minimized.

sthammadi-spsc commented May 11, 2016

Any update on when #151 will be fixed/closed?

@rkerber

This comment has been minimized.

Collaborator

rkerber commented May 11, 2016

No idea yet. #146 is the first one on my list to tackle then this one, and 146 is going to take a while longer to complete.

If anyone else wants to take a stab at this before I can get to it, go right ahead, let me know if you have any questions.

@sthammadi-spsc

This comment has been minimized.

sthammadi-spsc commented May 11, 2016

I hope #151 gets fixed quicker. Will make my life easy with unattended installs. Especially when i'm constantly tearing down and bring up my stage environment for continuous deployment and testing.

@ghost

This comment has been minimized.

ghost commented Jul 29, 2016

Manual client allows you to insert alternative names whereas command line have no such option. It would be great if there was an option to extract the certificate and key from the main file as Apache needs them seperate.

@rkerber

This comment has been minimized.

Collaborator

rkerber commented Jul 29, 2016

@dansali Take a look at #17 for apache support.

@ghost

This comment has been minimized.

ghost commented Jul 29, 2016

@rkerber Apache works good for me, it's mainly the additional names, because the certificate is only created for my domain and not the subdomain www. Manual mode within the application allows you to provide additional SAN's however the command line does not. It would be great if I can just automate this in one line rather than having to manually run it every couple of months.

nul800sebastiaan added a commit to nul800sebastiaan/letsencrypt-win-simple that referenced this issue Aug 6, 2016

nul800sebastiaan added a commit to nul800sebastiaan/letsencrypt-win-simple that referenced this issue Aug 6, 2016

nul800sebastiaan added a commit that referenced this issue Feb 25, 2017

@nul800sebastiaan

This comment has been minimized.

Contributor

nul800sebastiaan commented Mar 19, 2017

I'll close this as I think everything mentioned here is addressed in #275 which is available in v1.9.3 now.

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