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
fs3 compatibility #4158
Comments
I had not seen that and in principle it is the same. I was specifically talking about fs3 http://fs3.sourceforge.net/ which is similar in functionality. I am aware that it would need some updates to become fully compatible which I was going to use this wonderful application to work with. In the end there would be a better was to manage files in a scalable multi-server environment. I was simply thinking that if one can set the "base" hostname and S3 is treated like a protocol only, then this would be the best tool ever for managing them and it would promote use of centralize file services as well. In any event, a hat-tip you the author for coming up with the idea to integrate S3 into the file management tool. |
I would love I could test this out and give some feedback. In theory, if fs3 is API compatible it should just work. |
fs3 is still under development (by me) and if there is a way that I can set the base hostname for use by Cyberduck, I will definitely make the modifications necessary to support Cyberduck and recommend it as well. I agree if fs3 is compatible it should just work, but fs3 is a "subset" of the S3 service and I need to make sure it has what is required by your tool. |
Replying to [comment:5 sunsetbrew@…]:
It should work just fine by entering another hostname in the connection or bookmark setting. |
I had tried that but it seemed to assume the hostname I provided was a bucket name instead. It prepended it to the amazon S3 hostname. For example, if i enter fs3.somewhere.com in the server box, it tries to connect to fs3.somewhere.com.s3.amazonaws.com |
Here is how to recreate it.
The dialog result is Log reads: Summary: It is clear from the log that it never connected to the correct server, but instead connected to amazon's service and amazon treated the entered server name as a bucket (expected them to think it was bucket). Desired result is to make the request to the server of my choice. -** Never expected carbon (using fs3) to work especially since login is required, but connectivity would be a starting point. |
Replying to [comment:7 sunsetbrew@…]:
I fixed this in 58c56fb. A new snapshot is available in a few minutes. |
Thank you! I will get started on this and let you know when it is completed. |
I have a server that responds to amazon s3 api requests that is not hosted by amazon so i do not want to use the s3.amazonaws.com hostname. When I put a different hostname in, it just prepended it to that hostname. Is there anyway to work around this, so that the hostname I specify is that exact hostname used?
The text was updated successfully, but these errors were encountered: