TheDiscordian
TheDiscordian
For this feature to be stable, it should expect users to enable/disable this after sync, so we'll need to ensure the MFS is setup correctly upon change.
@kallisti5 is this a duplicate of #45? If so, I'll tag that issue for 0.8.0 release, and try to get 0.8.0 out sooner.
> Ideally it would check the CID of the file on disk vs the CID of the file in MFS, but that might not work out well :-) Now I...
Also if you're copying your IPFS db along with ipfs-sync, as long as the paths are identical and you also copied the ipfs-sync db over, it *should* not be going...
I've been thinking about this, and I want it to be as simple as possible. Like a password, security can be up to the user.
`files/cp` doesn't seem too slow. Will need more testing, but with #28 and #29 tackled, this issue doesn't impact nearly as much.
This issue can be closed after `files/write` is implemented, the switch can come in after #31 is complete (which isn't on the v1.0.0 milestone rn).
Actually not sure how important this is, so going to move it to the back-burner.
Instead of a switch, bulk add on init using #31, then add subsequent files / update using `files/write`.
Make it so the user can select what files/subdirectories they sync. For example, `["/"]` would sync everything, but `["/subdir", "/icon.png"]`, would sync a subdirectory and a file of the IPNS...