diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2017-07-12 12:44:21 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2017-07-12 12:44:21 -0400 |
| commit | b681b693fac4565e122953967ad0a8b54e5eda40 (patch) | |
| tree | 1515840f9ba82477296aa8745c29b7e5565a206a /doc/design | |
| parent | 207a757e49b98626a083a7f8f6a9ed73e9f559e5 (diff) | |
| parent | e68118be64df2b5d43708d9edd2ab18b2cc6e255 (diff) | |
Merge branch 'master' of ssh://git-annex.branchable.com
Diffstat (limited to 'doc/design')
3 files changed, 34 insertions, 0 deletions
diff --git a/doc/design/exporting_trees_to_special_remotes/comment_1_ea84ee9de604e05b8e02483ba8452186._comment b/doc/design/exporting_trees_to_special_remotes/comment_1_ea84ee9de604e05b8e02483ba8452186._comment new file mode 100644 index 000000000..c6e7c7aed --- /dev/null +++ b/doc/design/exporting_trees_to_special_remotes/comment_1_ea84ee9de604e05b8e02483ba8452186._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="note that some remotes could support files versioning "natively"" + date="2017-07-11T21:59:49Z" + content=""" +E.g. when exporting to the S3 bucket with versioning turned on, or OSF (AFAIK). So upon successful upload special remote could SETURLPRESENT to signal availability of any particular key (associated with the file). + +Yet to grasp the cases you outlined better to see if I see any other applicable use-ase + +I hope that export would be implemented through extending externals special remote protocol? ;) + +[[!meta author=yoh]] + +"""]] diff --git a/doc/design/exporting_trees_to_special_remotes/comment_2_d414fb575845770e003a3c8ca4a986be._comment b/doc/design/exporting_trees_to_special_remotes/comment_2_d414fb575845770e003a3c8ca4a986be._comment new file mode 100644 index 000000000..f0fc092ad --- /dev/null +++ b/doc/design/exporting_trees_to_special_remotes/comment_2_d414fb575845770e003a3c8ca4a986be._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="couldn't STATE be used for KEY -> FILENAME(s) mapping?" + date="2017-07-11T22:05:49Z" + content=""" +just wondered... +at least in my attempt for zenodo special remote I did store zenodo's file deposition ID within the state to be able to request it back later on +alternative -- URL(s) I guess. Could be smth like exported:UUID/filename. +"""]] diff --git a/doc/design/exporting_trees_to_special_remotes/comment_3_cb063cdc66df79c40039bce247b7170c._comment b/doc/design/exporting_trees_to_special_remotes/comment_3_cb063cdc66df79c40039bce247b7170c._comment new file mode 100644 index 000000000..377d167f7 --- /dev/null +++ b/doc/design/exporting_trees_to_special_remotes/comment_3_cb063cdc66df79c40039bce247b7170c._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="does it really need to be a new command ("export") or could be the same old "copy"?" + date="2017-07-11T22:14:39Z" + content=""" +or it could be just a mode of operation for a special remote depending on \"exporttree=true\" being set, where in one (old) case it would operate based on keys associated with the files pointed on the cmdline (or just keys for --auto or pointed by metadata), whenever when \"exporttree=true\" -- it would operate on filenames pointed on command line (or files found to be associated with the keys as pointed by --auto or by metadata)? +Then the same 'copy --to' could be used in both cases, streamlining user experience ;) +"""]] |