DNS Mapping for learn.eosnetwork.com

[kj4ezj]

I have been asked to assist in mapping learn.eosnetwork.com to a static page for Developer Relations. Originally, the page was already to exist on Netlify. The current plan is to host it ourselves either using the existing infrastructure for the documentation portal, or using an S3 bucket. In either case, this will still require DNS mapping plus some light work adding the static content to one of these locations.

See Also

• devrel issue 80 - Standup DevHub Infrastructure
  • The work requested for this ticket is a subset of what is necessary for that work, so you could think of this as a sub-task.
• devrel issue 96 - DNS Mapping for learn.eosnetwork.com
• devrel issue 134 - Update DevHub Site
• devrel issue 135 - DevHub Frontend CICD
• devrel issue 137 - Encrypt DevHub Backend
• devhub issue 12 - Put AWS Resources into Terraform with a CICD Deployment
• devhub issue 13 - Document CICD System
• devhub issue 14 - Staging Environment
• devhub issue 15 - Backend CICD
• devhub issue 16 - Structures CICD
• devhub issue 17 - Add a JavaScript/TypeScript Linter to the DevHub Projects
• devhub issue 18 - Add BASH Linters for CICD Code
• devhub issue 19 - Include Test Suite in CICD

[kj4ezj]

I pushed the contents of the nsjames/devhub-temp repo to eosnetworkfoundation/devhub-preregistration so the source code lives in the ENF organization, added an MIT license, tagged that with v1.0.0, cut "Release v1.0.0 - learn.eosnetwork.com Initial Deployment," and followed the steps documented there to publish the website to learn.eosnetwork.com on 2022-11-03, and informed the customer immediately.

The website is behind a content delivery network and should be "infinitely" scalable. I had actors test in the US East Coast, US West Coast, US Midwest, Europe, and Asia. Everyone claimed the site loaded in under one second.

The next step (not a part of this ticket) for this line of work will be to get the cloud infrastructure in Terraform.