-
Notifications
You must be signed in to change notification settings - Fork 11
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
Allow domain overrides for challenge delegation #2
Conversation
For more information, see libdns/duckdns#1 This commit adds Caddyfile parsing for an `override_domain` directive.
While you're at it, could you set the markdown code block language in the README to |
Done; changed that and fixed up a lingering |
Could you add a quick section above Also please add the new option to the example JSON config as well. |
Yep, something like that? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perfect. Thank you!
Co-authored-by: Francis Lavoie <[email protected]>
Co-authored-by: Francis Lavoie <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉
Done. I can rebase this all down to 1 commit if you prefer too, just let me know. |
No worry, I tend to squash merge. 😄 |
For more information, see libdns/duckdns#1
This commit adds Caddyfile parsing for an
override_domain
directive.
Should be pretty straightforward -- this adds
override_domain
in the same manner asapi_token
was being parsed. I did not add it as an argument to the main directive as I don't think it'll be as commonly used.I also changed the parsing for
api_token
-- unless I missed something, I think this wasn't working. ThatNextArg
call has to happen to get the parser to move on fromapi_token
to the provided value.Currently writing up a description of this in the README; I'll un-mark draft status once I have that up.