Cyberduck Mountain Duck CLI

Changes between Initial Version and Version 1 of Ticket #3241


Ignore:
Timestamp:
Jun 12, 2009 9:42:22 AM (11 years ago)
Author:
dkocher
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #3241 – Description

    initial v1  
    55The only thing where I ran into a road block in the whole process was when I tried to create a folder (bucket) on AS3. The rest was a breeze.
    66
    7 And if ducky prides itself of making things easy, hey, why not add a very small hint somewhere to 1) failed new folder (it says "/" not accepted or so) and 2) failed transfer (when trying to load a folder into root) and that hint would just say "folder name may not be S3-wide unique." And that would have been all that I needed to get my stuff up there and not think for some minutes, Cyberduck may be buggy, and in fact already looking for a different tool. It was by chance that I decided to look it up in Cyberduck's Help, after browsing Amazon for answers for a bit, querying the S3 dev docs.
     7 * And if ducky prides itself of making things easy, hey, why not add a very small hint somewhere to 1) failed new folder (it says "/" not accepted or so) and 2) failed transfer (when trying to load a folder into root) and that hint would just say "folder name may not be S3-wide unique." And that would have been all that I needed to get my stuff up there and not think for some minutes, Cyberduck may be buggy, and in fact already looking for a different tool. It was by chance that I decided to look it up in Cyberduck's Help, after browsing Amazon for answers for a bit, querying the S3 dev docs.
    88
    9 AND if you want to make life really easy, make the login name prompt "AWS ID", instead of "login" or "name" or what it was. Sure, it should be obvious. But then again, one has just signed in to AWS using an email address. Which at least I tried first and wondered.
     9 * AND if you want to make life really easy, make the login name prompt "AWS ID", instead of "login" or "name" or what it was. Sure, it should be obvious. But then again, one has just signed in to AWS using an email address. Which at least I tried first and wondered.
    1010
    1111Again, just trying to help. Great little tool & thanks for the pointer to S3.