Migration to landscape2 about graphql-landscape HOT 4 OPEN

OMG Yay! I didn't even realize we had a landscape v2, and I was just thinking I need to get it set up for some other projects. I think I can help with the DNS stuff, though I can't immediately find the record on graphql.org... so will have to do some digging. Thank you @tegioz !!

from graphql-landscape.

Thanks @jorydotcom!

Could you please create the following CNAME entries for us? We need them to prove that we are allowed to setup a certificate for those subdomains.

_d616d082e0014fef0b081f5543ccac18.landscape.graphql.org. -> _9deb6d30aaf056882afbe927deefd783.mhbtsbpdnt.acm-validations.aws.
_33000b4281f838c952a1f980c6791a1b.l.graphql.org. -> _487983a8444d7f7cbea305b4d0172ec1.mhbtsbpdnt.acm-validations.aws.

Once they are ready I'll update the list of hostnames and will share with you the new destination of the current landscape subdomains 🙂

from graphql-landscape.

@tegioz I think this is all set. Once we get GraphQL set up, I have some new projects to set up on v2!

from graphql-landscape.

Hi @jorydotcom

I think this is all set.

The CNAME entries for the certificate validation don't seem to be ready yet:

% host -t cname _d616d082e0014fef0b081f5543ccac18.landscape.graphql.org.
_d616d082e0014fef0b081f5543ccac18.landscape.graphql.org has no CNAME record
% host -t cname _33000b4281f838c952a1f980c6791a1b.l.graphql.org.
_33000b4281f838c952a1f980c6791a1b.l.graphql.org has no CNAME record

Once we get GraphQL set up, I have some new projects to set up on v2!

Awesome, looking forward to it 🙂

from graphql-landscape.