Hello. I want to say a big thank you right away for your fsarchiver product.
I am implementing an idea of the following nature: the files themselves are not stored in the archive, but on the ipfs host.
I think this can improve your product and expand its functionality.
This is done using REGFILE_NODATA, which is activated with the --no-data option. It is similar in structure to the REGFILE_UNIQUE of an empty file.
The files themselves are uploaded to the ipfs server using curl.
If I offer you a merge, can I expect to merge my code into the main branch, or are you not interested?
The code is still in a bad state, I implemented it only to test the idea itself.
I look forward to hearing, thank you very much.
Hello. I want to say a big thank you right away for your fsarchiver product. I am implementing an idea of the following nature: the files themselves are not stored in the archive, but on the ipfs host. I think this can improve your product and expand its functionality. This is done using REGFILE_NODATA, which is activated with the --no-data option. It is similar in structure to the REGFILE_UNIQUE of an empty file. The files themselves are uploaded to the ipfs server using curl. If I offer you a merge, can I expect to merge my code into the main branch, or are you not interested? The code is still in a bad state, I implemented it only to test the idea itself. I look forward to hearing, thank you very much.
Links: https://gitlab.com/mistikanil/fsarchiver-ipfs/-/tree/ipfs https://docs.ipfs.io/reference/http/api/#getting-started