Epic: Transfer peterp.org domain registration to Cloudflare Registrar
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- cloud
- Domain
- cloud, infrastructure
Research direction
Start with sub-issue #15 to identify the current registrar, unlock the domain, and retrieve its EPP code, then read Cloudflare’s transfer guide linked in the issue. Work through sub-issues #16–#18, checking DNS resolution after the transfer; completion means peterp.org is registered with Cloudflare and still resolves correctly. Re-check #19 for current cf CLI support before using the dashboard.
Written by the indexing model from the issue text.
Description
Goal
Transfer the registration of peterp.org from its current registrar to Cloudflare Registrar (at-cost pricing, single-pane management with the Worker).
Why
- Consolidates DNS, hosting, and registrar inside Cloudflare.
- Cloudflare Registrar charges domains at-cost.
Scope
Registrar transfer only. Hosting and code migration are tracked in #2 and #1.
Sub-issues
- #15 Identify current registrar; unlock domain & retrieve auth (EPP) code
- #16 Add peterp.org as a Cloudflare zone and update nameservers
- #17 Initiate registrar transfer in Cloudflare dashboard
- #18 Verify registrar transfer completion + DNS still resolves
- #19 Investigate whether the new cf CLI can drive the registrar transfer
Notes on the cf CLI
The cf CLI is in technical preview (npx cf / npm install -g cf) and only covers a small subset of products today; Registrar operations still require the dashboard or the Registrar API. Worth re-checking before doing the transfer manually \u2014 see #19.
Dependencies
- Independent of #1; can run in parallel.
- Custom-domain wiring on the Worker (#12) is simpler once nameservers are on Cloudflare (#16).
References
- Dominant language
- HTML
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from peterp/peterp.github.io
-
infrastructure
Difficulty 1/5 Under an hour Newbie friendliness 78/100
peterp/peterp.github.io#19 ·
-
infrastructure migration
Difficulty 1/5 Under an hour Newbie friendliness 68/100
peterp/peterp.github.io#14 ·
-
infrastructure migration
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
peterp/peterp.github.io#12 ·
-
infrastructure migration
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
peterp/peterp.github.io#11 ·
-
infrastructure migration
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
peterp/peterp.github.io#10 ·
All issues in peterp/peterp.github.io
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Cloudfront-rocoptiq): stable-staging: extras-rocoptiq origin missing OS-profile CloudFront rewriteOpen
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
hfile_s3: reading to EOF fails with EINVAL when object size is a multiple of the read part sizeOpen
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
boostorg/website-v2#2841 ·
Maintainers usually reply within 1 day
-
bug forward/review service/secretmanager
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
hashicorp/terraform-provider-google#29757 ·
Maintainers usually reply within 1 day