The edge reef

Every command of the edge reef: domains, zones and routes, in the order a person types them

O reef edge

Todos os comandos do reef edge: domínios, zonas e rotas, na ordem em que uma pessoa os digita

Setup

What comes before the first domain?

Preparação

O que vem antes do primeiro domínio?

Setup · reefbuilt #1949

One command applies the edge reef, with its first kind, Route

Preparação · reefpronto #1949

Um comando aplica o reef edge, com o seu primeiro kind, Route

~/example
# Apply the edge reef$ nereus reef apply edge✓ core/reefs/edge 0.1.0 created Next steps:   nereus edge --help  nereus nereid apply <nereid> --reef edge
Setup · tunnelbuilt #1949

The cloudflare Nereid runs the tunnel its Mandate names

Preparação · túnelpronto #1949

A Nereid cloudflare roda o túnel que o seu Mandate nomeia

~/example
# Apply the cloudflare Nereid to the edge reef$ nereus nereid apply cloudflare \    --reef edge✓ core/nereids/cloudflare created, Ready Next steps:   nereus mandate create cloudflare --reef edge --nereid cloudflare --param tunnel=<tunnel> --param credentialsSecret=edge/<secret> --default  nereus edge route create <name> --hostname <hostname> # Its Mandate: the named tunnel and its credentials, a secret of the secrets reef$ nereus mandate create cloudflare \    --reef edge \    --nereid cloudflare \    --param tunnel=nereus \    --param credentialsSecret=edge/cloudflare-tunnel \    --default✓ core/mandates/cloudflare created (reef: edge, nereid: cloudflare, default)
Setup · registrarplanned #475

The godaddy Nereid talks to the registrar, through its Mandate

Preparação · registradoraplanejado #475

A Nereid godaddy fala com a registradora, pelo seu Mandate

~/example
# Apply the godaddy Nereid to the edge reef$ nereus nereid apply godaddy \    --reef edge✓ core/nereids/godaddy created, Ready Next steps:   nereus mandate create godaddy --reef edge --nereid godaddy # Bind it to the reef$ nereus mandate create godaddy \    --reef edge \    --nereid godaddy✓ core/mandates/godaddy created Next steps:   nereus edge domain list --at-registrar --mandate godaddy
Zone

Who answers for the domain's names?

Zona

Quem responde pelos nomes do domínio?

Zone · createbuilt #1960

A zone gives the domain the nameservers that will answer for it

Zona · createpronto #1960

Uma zona dá ao domínio os nameservers que vão responder por ele

~/example
# Delegate the domain to the platform$ nereus edge zone create getnereus.dev \    --mandate cloudflare✓ edge/zones/getnereus.dev created, waiting for its delegation  nameservers: ada.ns.cloudflare.com, bob.ns.cloudflare.com  point the registrar of getnereus.dev at them; the zone turns Active once Cloudflare sees it Next steps:   nereus edge zone get getnereus.dev # Every zone and whether its delegation arrived$ nereus edge zone listNAME            MANDATE     STATUS   NAMESERVERSgetnereus.dev   cloudflare  Pending  ada.ns.cloudflare.com, bob.ns.cloudflare.com
Domain

Where does the registrar send the domain?

Domínio

Para onde a registradora manda o domínio?

Domain · list at the registrarplanned #475

The registrar shows its domains, with the credentials asked for now and never stored

Domínio · lista na registradoraplanejado #475

A registradora mostra os seus domínios, com as credenciais pedidas na hora e nunca guardadas

~/example
# What the registrar holds$ nereus edge domain list \    --at-registrar \    --mandate godaddyGoDaddy API key: ****GoDaddy API secret: ****NAME            NAMESERVERS                  EXPIRES      MANAGEDgetnereus.dev   ns01.domaincontrol.com (+1)  2029-10-25   noexample.com     ns01.domaincontrol.com (+1)  2029-10-25   noexample.org     ns01.domaincontrol.com (+1)  2028-06-11   no Next steps:   nereus edge domain get <name> --at-registrar --mandate godaddy  nereus edge domain apply <name> --mandate godaddy
Domain · applyplanned #475

Nereus takes the domain and sends it to the zone's nameservers

Domínio · applyplanejado #475

O Nereus assume o domínio e o manda para os nameservers da zona

~/example
# Delegate getnereus.dev to the zone$ nereus edge domain apply getnereus.dev \    --nameservers-from zone/getnereus.dev \    --mandate godaddy✓ domain/getnereus.dev created Next steps:   nereus edge domain get getnereus.dev --watch
Domain · listplanned #475

The list shows the domains Nereus looks after

Domínio · listplanejado #475

A lista mostra os domínios de que o Nereus cuida

~/example
# What Nereus looks after$ nereus edge domain listNAME            MANDATE  NAMESERVERS                 DELEGATEDgetnereus.dev   godaddy  ada.ns.cloudflare.com (+1)  True Next steps:   nereus edge domain get getnereus.dev
Domain · getplanned #475

One domain shows every detail, its nameservers one per line

Domínio · getplanejado #475

Um domínio mostra todos os detalhes, os nameservers um por linha

~/example
# Every detail of one domain$ nereus edge domain get getnereus.devName:         getnereus.devMandate:      godaddyDelegated:    TrueExpires:      2029-10-25Nameservers:  ada.ns.cloudflare.com  bob.ns.cloudflare.com  (from zone/getnereus.dev) Next steps:   nereus edge domain get getnereus.dev --watch
Route

How does a reef's endpoint get a name?

Rota

Como o endpoint de um reef ganha um nome?

Route · hostnamebuilt #1949

A route makes a hostname reach the platform

Rota · hostnamepronto #1949

Uma rota faz um hostname chegar à plataforma

~/example
# Carry Triton's hostname through the tunnel$ nereus edge route create triton \    --hostname triton.getnereus.dev✓ edge/routes/triton created, Ready: https://triton.getnereus.dev Next steps:   nereus edge route get triton # Every hostname the platform answers$ nereus edge route listNAME     HOSTNAME               ENDPOINT  MANDATE     READY   URLauth     auth.getnereus.dev     -         cloudflare  True    https://auth.getnereus.devportal   portal.getnereus.dev   -         cloudflare  True    https://portal.getnereus.devtriton   triton.getnereus.dev   -         cloudflare  True    https://triton.getnereus.dev
Route · endpointsbuilt #1951

The Nereids say what they serve, never where it runs

Rota · endpointspronto #1951

As Nereids dizem o que servem, nunca onde rodam

~/example
# What the Nereids serve at the instance's entrance$ nereus edge endpoint listREEF       ENDPOINT  NEREID  PROTOCOL  PATHS  HOSTS               PUBLISHABLE  PUBLISHED  ROUTESmessaging  mcp       triton  http      /      triton.example.com  yes          no         - # Grant it: only an endpoint its Nereid's spec.publish names is ever published$ nereus nereid apply triton \    --publish mcp✓ core/nereids/triton unchanged, Ready✓ core/nereids/triton configured (publishes: mcp)
Route · createbuilt #1951

A route publishes a reef's endpoint at a fixed address

Rota · createpronto #1951

Uma rota publica o endpoint de um reef num endereço fixo

~/example
# Publish Triton's MCP endpoint$ nereus edge route create triton \    --hostname triton.example.com \    --endpoint messaging/mcp✓ edge/routes/triton created, Ready: https://triton.example.com Next steps:   nereus edge route get triton # Not granted: the Route stays, and says what is missing$ nereus edge route create docs \    --hostname docs.example.com \    --endpoint messaging/admin✗ timed out after 120s waiting for edge/routes/docs to be Ready (Ready: NotPublishable: <its Nereid's message>); it is left as it is: see 'nereus edge route get docs'