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
We want to be able to have more control over the synchronized asset folder, making it possible to clean it up (currently, once an item is synced, it's very hard to get rid of it or move it).
The use of sentinel filenames and command line flags probably provides the solution:
Default sync resolution
If a file does not exist on the local but does exist on remote (or vice versa), it's copied so that it exists in both places.
If a file exists in both places, the newer file is treated as the source, and copied over the older versions.
If the remote file has the suffix _deleted (or another sentinel, it's not important), it will be removed from the local folder.
--push
Local files are pushed up and replace any remote files.
No files are downloaded or deleted locally.
--push --force
Same process as regular --push, except
If a file is on the remote but not local, it is renamed on the remote with the _deleted suffix so that it will be removed from other clients.
If the remote folder has a _deleted file but we have a local file with the same name, the _deleted file is removed and the local file is uploaded.
--pull
Remote files are downloaded only.
If a file is marked with _deleted on the remote, it's removed from the local.
No files are uploaded.
We should also probably add a --file=PATTERN flag to support filtering a subset of files from the local/remote, which would make it easier to selectively update the folder with deletions.
The text was updated successfully, but these errors were encountered:
We want to be able to have more control over the synchronized asset folder, making it possible to clean it up (currently, once an item is synced, it's very hard to get rid of it or move it).
The use of sentinel filenames and command line flags probably provides the solution:
Default sync resolution
_deleted
(or another sentinel, it's not important), it will be removed from the local folder.--push
--push --force
--push
, except_deleted
suffix so that it will be removed from other clients._deleted
file but we have a local file with the same name, the_deleted
file is removed and the local file is uploaded.--pull
_deleted
on the remote, it's removed from the local.We should also probably add a
--file=PATTERN
flag to support filtering a subset of files from the local/remote, which would make it easier to selectively update the folder with deletions.The text was updated successfully, but these errors were encountered: