Closed dignifiedquire closed 8 years ago
Travis fails because it's not pinned on the 0.3 network probably and the resolves are too slow due to that
woooooo. Do we really want to push the dataset to the repo?
Codewise LGTM :) great work @dignifiedquire !! Finally we have geoip working with proper tests and more docs :) :dancer:
One request, if all that travis needs is to have the dataset pinned on 0.3, can we do that to see if it goes green? It will be also useful for anyone else that might want to contribute as well.
woooooo. Do we really want to push the dataset to the repo?
I don't know, I'd rather have it checked in than go search for it again in the future tbh
One request, if all that travis needs is to have the dataset pinned on 0.3, can we do that to see if it goes green? It will be also useful for anyone else that might want to contribute as well.
I want to make it green, but pinbot keeps dying when trying to pin it :(
I don't know, I'd rather have it checked in than go search for it again in the future tbh
Let's put it into IPFS and pin.
This dataset: ipfs.io/ipfs/<hash1>
produces this merkledag: ipfs.io/ipfs/<hash2>
Latest dataset available here: someurl.com/dataset.tgz
Yes, put it into IPFS, not this repo. We should pin it.
(We should look into making a pinbot that works with github repos.)
@lgierth @jbenet done, all data is now on ipfs, and gets downloaded automatically when generate is run :)
Great :+1: could you squash the commits so that we don't bloat the repo size unneccessarily?
@lgierth will do. any updates on pinning location data on 0.3? pinbot always dies
@dignifiedquire would be nice to make CI pass the tests, that way merging changes is way easier / safer. fine to be a new issue + separate PR.
@jbenet they will pass when 0.3 has the geo data
Merging this for now, tests will work as soon as the 0.3 issues are resolved. But I need a new release for use in ipfs/webui.
What is blocking us from pinning it on 0.3? Is there an issue in infrastructure to track that progress that can be linked from here?
What is blocking us from pinning it on 0.3? Is there an issue in infrastructure to track that progress that can be linked from here?
nothing -- I'm on it
data
)QmRn43NNNBEibc6m7zVNcS6UusB1u3qTTfyoLmkugbeeGJ
)Fixes #6