Skip to content
This repository has been archived by the owner on Mar 25, 2022. It is now read-only.

update.ipfs.io dnslink? #139

Closed
jbenet opened this issue Dec 16, 2015 · 7 comments
Closed

update.ipfs.io dnslink? #139

jbenet opened this issue Dec 16, 2015 · 7 comments

Comments

@jbenet
Copy link
Member

jbenet commented Dec 16, 2015

quick q: where is the TXT record set for update.ipfs.io ? i didnt find it in digital ocean

@jbenet
Copy link
Member Author

jbenet commented Dec 16, 2015

It should now be set to:

/ipfs/QmeEVmRTDX2c9zjPtjHJG6GidrFL7NjqEqP1Q4am6sLfif

@whyrusleeping did you add this elsewhere?

@whyrusleeping
Copy link
Member

its on digitalocean, i'll update it and post the process (maybe i did things weirdly?)

@whyrusleeping
Copy link
Member

So, on digitalocean, i click the networking tab, then the domains side-tab thing, then i click the magnifying glass next to ipfs.io.

When I made the record it didnt let me make the TXT record as its own entry on the main page.

@jbenet
Copy link
Member Author

jbenet commented Dec 16, 2015

@whyrusleeping oh i see added it under one domain. i guess that's ok? there's multiple ways to do it because can treat a subdomain as a domain

@jbenet
Copy link
Member Author

jbenet commented Dec 16, 2015

@whyrusleeping pro tip: use https://github.com/ipfs/dnslink-deploy and something like: https://github.com/ipfs/website/blob/master/Makefile#L30-L32

i think will want:

DIGITAL_OCEAN=$(shell cat auth.token) node_modules/.bin/dnslink-deploy \
        --domain=ipfs.io --record=update --path=/ipfs/$(shell cat versions | tail -n1)

or

> cat publish-dnslink
#!/bin/sh

token="$(cat auth.token)"
path="/ipfs/$(cat versions | tail -n1)"
domain="update.ipfs.io"

echo "publishing $path at $domain"
DIGITAL_OCEAN="$token" dnslink-deploy \
  --domain="$domain" \
  --record="@" \
  --path="$path"

@ghost
Copy link

ghost commented Feb 1, 2016

@whyrusleeping let me know when ipfs-update uses dist.ipfs.io, then I'll go and delete update.ipfs.io

@ghost
Copy link

ghost commented Apr 5, 2016

Closing this. I had deleted the update.ipfs.io records in the meantime, but then it turned out the currently released version of ipfs-update (1.0.0) still uses it -- meh! Reinstated it, and I guess it's there to stay.

@ghost ghost closed this as completed Apr 5, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants