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
Along with files, rclone/SFTP could download a metadata package that has all the metadata that the user has added (i.e., via the Permanent web UI) corresponding to those files. Then one day we could support upload/sync of that metadata. It would be in a file named .permanent-metadata.json or something like that.
The text was updated successfully, but these errors were encountered:
Note that this could affect the user's need to use the --create-empty-src-dirs with rclone, since now (from rclone's point of view) the directories wouldn't be empty anymore.
Just to clarify on the above observation -- we talked about the idea of potentially creating some kind of gitkeep equivalent for folders (or metadata for folders / archives).
This issue as written is more focused on file metadata (which, if a file exists, the folder would already be non-empty)
Along with files, rclone/SFTP could download a metadata package that has all the metadata that the user has added (i.e., via the Permanent web UI) corresponding to those files. Then one day we could support upload/sync of that metadata. It would be in a file named
.permanent-metadata.json
or something like that.The text was updated successfully, but these errors were encountered: