Open kallisti5 opened 11 months ago
I originally considered this. Here's why I didn't do that:
The way I used ftp2mfs was to sync, and then do ipfs files stat --hash /stuff/data
and publishing that to ipfs name
and some dnslinks.
With what you suggest, you'd do ipfs files stat --hash /stuff
, but then the folder you publish would contain some weird extra files. I wouldn't like that.
You could of course sync to /.stuff-sync
and then always copy /.stuff-sync/data
to /stuff
after syncing.
If you want to try patching that, does just making this bunch of functions https://github.com/jcaesar/ftp2mfs/blob/d7b9c4a3691437902f974f2fb448ecd1dbb06bac/src/tomfs.rs#L36-L68 return the set of values you want work correctly? (There is some copy/modify/replace-original magic going on, so it might not.)
Ah yeah, so my issue is i'm syncing several things from various locations into one set of directories i'm publishing to ipns.
Publish / -> ipns dnslink
Just noticed that ftp2mfs modifies the data too much.
config:
source:
destination:
Wouldn't it make more sense to maintain the file structure and add a hidden state directory?
For example: destination: