Uploading file(s) API

happybeing · April 8, 2024, 9:43pm

I could do with some guidance on use of the API to upload a file, or ideally a directory tree and obtain a list of the xor address for each uploaded file.

I’ve written an app which can do the upload using the FilesUploader::start_upload() API that successfully uploads a tree, but cannot find a way to obtain the xor addresses for the datamap for each path in the tree.

The ChunkManager used internally in this process has this information but it is not included in the UploadSummary returned to the app.

I suspect I’m using the wrong APIs so what would be the recommended way for an app to do this?

joshuef · April 9, 2024, 12:48am

hmm cc @bochaco on this, I’m not sure myself.

happybeing · April 9, 2024, 9:56am

Thanks Josh, this is now being looked into here:

github.com/maidsafe/safe_network

API for uploading a directory tree - some questions

opened 04:55PM - 05 Apr 24 UTC

happybeing

I'm looking for an API for uploading a directory tree. The `sn_cli` `ChunkManage…r` seems to do everything I need, but once it completes I don't see a way for the app match the *path* of an uploaded file to the xor address of its datamap. The `ChunkManager` keeps track of the filenames and their xor addresses, but not the paths to the files. I assume there isn't an alternative API that allows uploading of a directory tree, and tracks the paths. So would you consider a PR to modify the `ChunkManager` to track the path of the file (and/or the name, since the name can be obtained from the path if that is retained)? In the short term it may be easier for me to build a separate crate with the API I need (and modified `ChunkManager`). So an alternative would be for me to do that and at some point the `sn_cli` could be modified to use that. So I'm curious if these APIs might be better separated from the `sn_cli` crate which doesn't seem to be a good location for things used by other apps. Any thoughts?

happybeing · April 9, 2024, 1:25pm

Fixed: