-
Notifications
You must be signed in to change notification settings - Fork 481
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
Import/export CAR DAG archives #1798
Comments
Seems like it would be a good idea to do it after ipfs/js-ipfs#2745 |
@lidel as I mentioned on #1838 (comment), we'll need to update to the latest HTTP client across WebUI and the Explore page to support the import part. The export is done on #1837. I don't think I should work on the upgrade right now as that would take a long time working only 10h a week. Updating the http client will also require updating everything else connected: multiformats, ipld, multicodecs, etc. I think we could merge the export button and evaluate how much effort is needed for the import part. |
On ipfs-http-client API updateAgree that upgrading http-client and all the deps (especially ipld-explorer-components) will be a time sink (due to API changes and refactors). On import UXIn regard to CAR Import/export – I am a bit hesitant to introduce export without the ability to import it as well. I think we not only need |
@lidel I agree with your worry. I didn't think about that, but it's a good point. |
Reopening since we also need #1838 |
Add maximum CAR size so output can be split into multiple files. Standard between storage services seems to be accept 100 MB CAR files for uploads. |
@hsn10 that is an artificial limitation of some specific services. Users of such services can do the splitting with third-party tools like carbites. We could integrate carbites splitter into ipfs-webui, but it would be pretty expensive to implement, and require additional UI design (how to opt into splitting, how to control splitting parameters, what should be the default). |
Given that:
ipfs dag import|export
exists/api/v0/dag/export
)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:
The text was updated successfully, but these errors were encountered: