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

Improving ACME-related docs #82

Merged
merged 4 commits into from
Sep 4, 2016
Merged

Conversation

ser
Copy link
Contributor

@ser ser commented Sep 4, 2016

No description provided.

@@ -153,6 +153,33 @@ configuration active, it will check for validity of the signed certificate, and
about a month before the expiration date it will try to renew the certificate
automatically.

I want a certifcate for subdomains but domain
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"but not the apex domain"

@drybjed drybjed merged commit 852904c into debops:master Sep 4, 2016
ypid added a commit to ypid/ansible-pki that referenced this pull request Sep 6, 2016
* Remove "I want a" from title :)
* The ACME severs is unspecific.
* `pki_acme` is unrelated to this section.
* Comments after YAML variables might case problems in certain YAML
  modes and should thus be avoided.
* Use the more specific term "apex domain" as already suggested by
  @drybjed in: debops#82 (comment)

Related to: debops#82
Wanted confirmation from: @ser, @drybjed
@ypid
Copy link
Member

ypid commented Sep 6, 2016

Hey guys. I just rebased ontop of this PR and reworked it a bit as well in #81. Is this ok with you?

@drybjed
Copy link
Member

drybjed commented Sep 6, 2016

Sounds good to me, although I would revise the note about the realm name as commented.

ypid added a commit to ypid/ansible-pki that referenced this pull request Sep 12, 2016
* Remove "I want a" from title :)
* The ACME severs is unspecific.
* `pki_acme` is unrelated to this section.
* Comments after YAML variables might case problems in certain YAML
  modes and should thus be avoided.
* Use the more specific term "apex domain" as already suggested by
  @drybjed in: debops#82 (comment)

Related to: debops#82
Wanted confirmation from: @ser, @drybjed
@ypid ypid mentioned this pull request Sep 12, 2016
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

Successfully merging this pull request may close these issues.

3 participants