Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Editable URL for S3 bookmark #3125

Closed
cyberduck opened this issue Apr 23, 2009 · 6 comments
Closed

Editable URL for S3 bookmark #3125

cyberduck opened this issue Apr 23, 2009 · 6 comments
Assignees
Labels
enhancement fixed s3 version:3.1.2
Milestone

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Apr 23, 2009

5cfbca2 created the issue

I know of a number of cloud companies that are making a replica of the S3 API for their own cloud. To be able to use Cyberduck as the client tool to access the files, I would like the S3 URL field to be editable when I create an S3 account. This way, I can use Cyberduck beyond the real Amazon S3.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 23, 2009

@dkocher commented

Some [source:trunk/source/ch/cyberduck/core/ec work] has been done to support [Eucalyptus http://eucalyptus.cs.ucsb.edu/] already. I tested against the [public installation http://eucalyptus.cs.ucsb.edu/wiki/EucalyptusPublicCloud] where uploads fail and therefore it is not currently enabled yet.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 23, 2009

@dkocher commented

The actual Walrus error message is Could not identify the operation component of the request when issueing a HEAD request on a bucket.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 23, 2009

@dkocher commented

Replying to [3125 ringods]:

I know of a number of cloud companies that are making a replica of the S3 API for their own cloud. To be able to use Cyberduck as the client tool to access the files, I would like the S3 URL field to be editable when I create an S3 account. This way, I can use Cyberduck beyond the real Amazon S3.

Do they use other implementations than Eucalyptus?

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 29, 2009

5cfbca2 commented

Replying to [comment:4 dkocher]:

Do they use other implementations than Eucalyptus?

Yes, they have a complete implementation of their own (closed source). Is there a Cyberduck build somewhere that I can use to test against their implementation?

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 29, 2009

@dkocher commented

Replying to [comment:5 ringods]:

Replying to [comment:4 dkocher]:

Do they use other implementations than Eucalyptus?

Yes, they have a complete implementation of their own (closed source). Is there a Cyberduck build somewhere that I can use to test against their implementation?

You have to build from source and enable and add Protocol.EUCALYPTUS to the list of known protocols in [source:trunk/source/ch/cyberduck/core/Protocol.java#L487]. This protocol then selectable from the popup in the bookmark dialog will allow you to change the hostname. It is configured not to use DNS bucket names and allows to set an endpoint other than / in [source:trunk/source/ch/cyberduck/core/ec/ECSession.java#L62].

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 31, 2009

@dkocher commented

In 3f53c22.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement fixed s3 version:3.1.2
Projects
None yet
Development

No branches or pull requests

2 participants