-
Notifications
You must be signed in to change notification settings - Fork 4
Open
Description
Hey @systemantix @clementbriens @edsaperia, going to stub out what it would take to manage newspeak.link via this repo, in case you're open to it. Worst case scenario, this was a good chance to better-document the process 🙂
Steps of Process
Full documentartion of steps [in theory] are detailed here: https://github.com/g0v-network/domains/blob/main/docs/HOWTO.md#domains
(Pull requests with doc improvements very welcome.)
Role Legend
👒 g0v-network/domains repo maintainer must do this, aka @patcon
💪 PR submitter (or anyone) can do this, but likely either you or me
👑 domain owner must do this, aka clement
- 👒 add
newspeak.linkdomain to Cloudflare account (status will be "pending transfer") [screenshot] - 👒 import existing DNS records into pending Cloudflare domain
- 👒 enable management of pending domain under the Cloudflare API key
- 💪 create a minimal config file at
newspeak.link.domain/newspeak.link.yaml, [see branch] - 💪 transfer any existing DNS records into config file(s), in this case just
newspeak.link.domain/newspeak.link.yaml, [see branch] - 💪 add entry for
newspeak.linktoconfig.yaml[see branch] - 💪 create a PR with the above config changes (Add newspeak.link #42)
- 🚧 If Cloudflare preparation has already been done, an automated comment from CI will do a dry-run and show any differences between YAML config files and the "live" DNS records
- 👒 if looks good, merge the PR
- 👑 change DNS nameservers (on Tucows?) to point to Cloudflare nameservers:
clyde.ns.cloudflare.com tina.ns.cloudflare.com - 💪 confirm nameservers are switched by check NS records:
host -t ns newspeak.link - 👒 give push access on
g0v-network/domainstonewspeak.linkdomain owner (though future expectation is to work via PRs like this) - 💪 document in
clementbriens/newspeak-shortlinkhow the domain is managed.
Metadata
Metadata
Assignees
Labels
No labels