Skip to content

update now.json #2434

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 17, 2019
Merged

update now.json #2434

merged 2 commits into from
Apr 17, 2019

Conversation

Rich-Harris
Copy link
Member

Trying to deploy the site to https://svelte.dev. So far doesn't seem to work — I get this in my terminal after running Now:

> Assigning alias svelte.dev to deployment sveltedev-kbseobnwsd.now.sh
> Error! We couldn't verify the propagation of the DNS settings for svelte.dev
  The propagation may take a few minutes, but please verify your settings:

name        type         value
            ALIAS        alias.zeit.co
error Command failed with exit code 1.

Namecheap doesn't appear to give me the option of assigning an ALIAS record... will have to come back to this when less busy

@codecov-io
Copy link

codecov-io commented Apr 17, 2019

Codecov Report

Merging #2434 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #2434   +/-   ##
=======================================
  Coverage   91.83%   91.83%           
=======================================
  Files           1        1           
  Lines          49       49           
=======================================
  Hits           45       45           
  Misses          4        4

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 519059f...d7b51a3. Read the comment docs.

@Conduitry
Copy link
Member

I don't think there's a real official ALIAS DNS record. It looks like some DNS providers allow it as a workaround for root domains not allowing CNAME records. It causes the DNS provider to look up, cache, and return the A record from some other domain.

You should probably just set the same A record(s) as are on svelte.technology and/or on alias.zeit.co.

@Conduitry
Copy link
Member

dig shows the same two A records for svelte.technology and alias.zeit.co, as expected.

...
;; ANSWER SECTION:
svelte.technology.      60      IN      A       3.86.168.228
svelte.technology.      60      IN      A       3.210.90.207
...
...
;; ANSWER SECTION:
alias.zeit.co.          60      IN      A       3.86.168.228
alias.zeit.co.          60      IN      A       3.210.90.207
...

Setting static A records for svelte.dev (rather than having ones that query and cache alias.zeit.co) will break if alias.zeit.co's A record changes, but I would imagine Zeit has a rather large vested interest in that not happening.

@Conduitry
Copy link
Member

Correction for posterity: alias.zeit.co's A records are themselves dynamic, presumably via Cloudflare magic. So we don't want to point at those. Instead svelte.dev's nameservers are going to be set to Zeit's, so they can take care of all the DNS stuff.

@Conduitry
Copy link
Member

We also need to make sure the repl github oauth app has its authorization URL and BASEURL etc set appropriately.

@Conduitry
Copy link
Member

https://svelte.dev/ is now up and running for me - but the github auth stuff is not working, as it still needs to be updated.

@Rich-Harris Rich-Harris merged commit 1f34c2e into master Apr 17, 2019
@Rich-Harris Rich-Harris deleted the svelte-dev branch April 17, 2019 15:26
@Rich-Harris
Copy link
Member Author

Looks like everything is working. https://svelte.dev is our new home.

At some point I'll deploy the current https://svelte.technology as https://v2.svelte.dev, and move over https://sapper.svelte.technology and https://hn.svelte.technology to their .dev counterparts (I think that's everything on svelte.technology)

@Rich-Harris
Copy link
Member Author

Oh and 301 v3.svelte.technology to svelte.dev, obvs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants