You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would also be nice, if the files added to IPFS could be saved in the MFS instead of in pins.
For this, a folder-name would need to be specified in the config for a single git. git-lfs-ipfs would then run ipfs add with the parameter --to-files= followed by a filename for the file.
Something like “/$configured_folder/path/in/git-repo/$commitID-$filename” would probably be the best.
Using this, you can also set --pin=0 to avoid pinning the file, which gets messy fast - as there's no overview over the data stored. So you end up with just a bunch of numbers without no reference.
This also ensures that the users can easily push the folder to a remote pinning service via the GUI.
The text was updated successfully, but these errors were encountered:
It would also be nice, if the files added to IPFS could be saved in the MFS instead of in pins.
For this, a folder-name would need to be specified in the config for a single git. git-lfs-ipfs would then run
ipfs add
with the parameter--to-files=
followed by a filename for the file.Something like “/$configured_folder/path/in/git-repo/$commitID-$filename” would probably be the best.
Using this, you can also set
--pin=0
to avoid pinning the file, which gets messy fast - as there's no overview over the data stored. So you end up with just a bunch of numbers without no reference.This also ensures that the users can easily push the folder to a remote pinning service via the GUI.
The text was updated successfully, but these errors were encountered: