Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Import/export CAR DAG archives

See original GitHub issue

Given that:

ipfs dag import|export exists
go-ipfs 0.9+ supports exporting DAG archive via any public gateway (/api/v0/dag/export)
tools like ipfs-car and ipfs-content-addressed-archiver make it easier for people to produce/consume content-addressed archives

We should support “DAG import/export” in ipfs-webui somehow.

Import DAG

Import could work the same as “From IPFS” :

We most likely want to add an explicit “From CAR Archive” item here (personally, I like the idea of a whimsical car icon 😃), but “stroke data” from ipfs-css would also do.

Export DAG

Add complimentary “Export DAG” to context menu on Files screen:

Issue Analytics

State:
Created 2 years ago
Comments:7 (6 by maintainers)

Top GitHub Comments

2reactions

Gozalacommented, Jun 23, 2021

Seems like it would be a good idea to do it after https://github.com/ipfs/js-ipfs/issues/2745

1reaction

lidelcommented, Sep 2, 2021

On ipfs-http-client API update

Agree that upgrading http-client and all the deps (especially ipld-explorer-components) will be a time sink (due to API changes and refactors). I’ll block some time on Friday to understand the scope bit better and decide what’s next.

On import UX

In regard to CAR Import/export – I am a bit hesitant to introduce export without the ability to import it as well.
Main worry: people will import .car via Import→File and produce garbage blocks (CAR with original DAG wrapped into redundant dag-pb DAG)

I think we not only need Import→DAG Archive but also make Import→File check for magic bytes and do DAG import instead of importing CAR as binary unixfs file.