Sounds good. The first integration step would be to create a ​profile with preconfigured settings for Lunacloud that can be downloaded, and when opened adds such a pre configured connection setting. See for example the profile for ​GreenQloud.

I wonder if you support all the AWS features such as versioning and logging configuration?

Lunacloud Cyberduck Profile

Hello,

We already create the Cyberduck Profile and we are elaborating the web page.

Please find in attach the profile and let us know if you have any considerations. After we finish the web page we will send it to you.

For the moment we are not supporting versioning and the logs need to be checked by the management console but we will support that in future releases.

Regards,

Hugo Tavares

That profile looks perfectly fine. Great you could already figure this out. We can then create a wiki page with it and you can share it with your customers. You could also prefill the username (Access Key ID) dynamically for users logged into your console.

Hello dkocher,

Just to give you an update we are working on the documentation and when it's available we send you the wiki page.

Regards,

Hugo Tavares

Please edit the lunacloud wiki page.

Hello dkocher,

I'm not able to submit the changes because it considers as spam! (too many links?)

Do we need to remove links or should I try to send you the file for any other away? (by the attach it's not also possbile:

Submission rejected as potential spam (Maximum number of external links per post exceeded) Trac thinks your submission might be Spam. To prove otherwise please provide a response to the following. Input error: k: Format of site key was invalid

Thx

Hugo

Replying to lunacloud:

Hello dkocher,

I'm not able to submit the changes because it considers as spam! (too many links?)

Do we need to remove links or should I try to send you the file for any other away? (by the attach it's not also possbile:

Submission rejected as potential spam (Maximum number of external links per post exceeded) Trac thinks your submission might be Spam. To prove otherwise please provide a response to the following. Input error: k: Format of site key was invalid

Thx

Hugo

Is this by editing the wiki page? Yes, try removing the links and add them later again.

Ok dkocher, we did some "cosmetic" and it's ok now.

Do you know when it will be release the profile with the cyberduck app?

Regards,

hugo

I have for now decided against including more profiles by default for S3 compatible providers. But you are more than welcome to make the profile available to your customers to make setup a breeze.

Hi,

Any change you can review that decision for our case and include our profile. We'd be willing to contribute (donate) to the project as well as promote actively Cyberduck in the Cloud Storage section of our site, when we launch it late May. If yes, great. If not, thanks for your support anyway and good luck with Cyberduck, it's a good product!

Replying to lunacloud:

Hi,

Any change you can review that decision for our case and include our profile. We'd be willing to contribute (donate) to the project as well as promote actively Cyberduck in the Cloud Storage section of our site, when we launch it late May. If yes, great. If not, thanks for your support anyway and good luck with Cyberduck, it's a good product!

We can always reconsider this for the future but currently I am hesitant to such a step as there are many more stakeholders that would like their own profile included. But this fragmentation is somewhat not justified I think. In the end I need to include an option for every single hosting provider.

Replying to dkocher:

Replying to lunacloud:

Hi,

Any change you can review that decision for our case and include our profile. We'd be willing to contribute (donate) to the project as well as promote actively Cyberduck in the Cloud Storage section of our site, when we launch it late May. If yes, great. If not, thanks for your support anyway and good luck with Cyberduck, it's a good product!

We can always reconsider this for the future but currently I am hesitant to such a step as there are many more stakeholders that would like their own profile included. But this fragmentation is somewhat not justified I think. In the end I need to include an option for every single hosting provider.

In fact that is the reason why I have added support for optional profiles being available as plugin files for providers that want to make it easier for their customers with preconfigured settings.