caddyserver / caddyserver/certmagic
Q: What's the correct way to setup statically managed domains + dynamically added domains?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.6k
- Forks
- 354
- Avg merge
- 9d 23h
- Merged PRs (30d)
- 3
Description
Use case: I have a project that allows users to create reverse tunnel over QUIC, and their tunnels will be available on tunnel.example.com, such as string-string-string.tunnel.example.com. However, I also want to allow user to point their own domain to the service.
Currently there's ManageAsync on tunnel.example.com and *.tunnel.example.com, with only DNS solver available. Assuming that the "custom hostname" is web.mydomain.com, and its TXT record is managed by the service, how would you dynamically add that to a running certmagic instance?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the ManageAsync flow for the statically managed hostnames and the running certmagic instance described in the report. Trace how a custom hostname and its service-managed TXT record are handled, then document or specify the supported workflow for adding that hostname dynamically without restarting the instance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100