Closed
Conversation
jamesward
reviewed
Dec 6, 2016
| </p> | ||
| <h4>Renewal Note</h4> | ||
| <p> | ||
| If you’re renewing a certificate, previously used the file-based method, and did not delete the verification file from your server, you should not need to regenerate the signature but can simply verify using the existing file. |
There was a problem hiding this comment.
These instructions could be more clear. I'm not sure what they actually mean. Should I not use the Run this signature command in your terminal: form?
Owner
|
In v2, added a line saying that to renew just run through the steps again. Line 97 in bd24e41 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Sorry, based this on top of #106 so it won’t be a clean merge if you don’t want those changes.
Helps with #104 and #76.