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
Cyberduck's feature tag line made me aware of Amazon S3.
It was easy to set up an account at Amazon to give it a try. Without too much reading. I know, RTF. But. I had done enough serious things that day and read my scores of man pages.
The 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.
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.
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.
Again, just trying to help. Great little tool & thanks for the pointer to S3.
The text was updated successfully, but these errors were encountered:
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.
Currently this is only shown as the placeholder text in the username and password login fields. However the placeholder text is not seen when the text field has focus so we should change the label as well.
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.
The error message displayed says Conflict The requested bucket name is not available. The bucket namespace is shared by all users of the system. Please select a different name and try again.
Cyberduck's feature tag line made me aware of Amazon S3.
It was easy to set up an account at Amazon to give it a try. Without too much reading. I know, RTF. But. I had done enough serious things that day and read my scores of man pages.
The 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.
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.
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.
Again, just trying to help. Great little tool & thanks for the pointer to S3.
The text was updated successfully, but these errors were encountered: