feat: use custom domain linkdex.dag.haus

[olizilla]

prod lives at linkdex.dag.haus
staging is at staging.linkdex.dag.haus

...all non-prod stages follow that pattern ${stage}.linkdex.dag.haus

License: MIT
Signed-off-by: Oli Evans oli@protocol.ai

[olizilla]

linkdex.dag.haus is updated in cloud flare to use route53 nameservers

[seed-deploy]

View stack outputs

• pr4-linkdex-api-LinkdexStack

  Name	Value
  ApiEndpoint	https://o0dieuajb1.execute-api.us-east-2.amazonaws.com

[seed-deploy]

Stack outputs updated

• pr4-linkdex-api-LinkdexStack

  Name	Value
  ApiEndpoint	https://o0dieuajb1.execute-api.us-east-2.amazonaws.com
  CustomDomain	https://pr4.linkdex.dag.haus

[vasco-santos]

Changes look good. For consistency with all other projects I would go with linkdex-staging like we do for api-staging.*, ipfs-staging.*, and so on

[olizilla]

@vasco-santos good point! Alas, that would be difficult to implement here as the dag.haus domain is managed on cloudflare not route53. The trick that makes this work at all is the subdomain linkdex.dag.haus is manually delegated to route53 name servers. I could special case staging and delegate both linkdex.dag.haus and linkdex-staging.dag.haus but I prefer the look of ${stage}.linkdex.dag.haus and the original reason for the api-staging pattern was that it was hard to generate all the necessary SSL certificates for sub-sub-domains, which isn't the case here.