Problem using Noc Storage (Planethoster)

[rvrignaud-cmaisonneuve]

Describe the bug

Hello,

I wanted to use your plugin to link omeka with amazon s3. My host (PlanetHoster) uses its own solution ‘Noc Storage’ which uses Amazon S3 but when I set your Any Cloud module to link with Noc Storage it doesn't work. I can't upload files, I don't get any error messages. My hosting provider told me that I should add the public ‘path’ in the configuration of the ‘Any Cloud’ module. This is because in my Noc Storage space I have to choose the ‘Public’ or ‘Private’ folder. Is it possible to do this with your module?

Thanks in advance.

Romain

[PHMarcAndreB]

Hello,

We are joining this discussion as the PlanetHoster support team for the current request.

PlanetHoster offers an S3-compatible object storage solution called N0C Storage, which uses self-hosted custom endpoints. Once connected via the --endpoint-url method, each bucket contains two main folders (paths):

-private (non-public)

-public (for publicly accessible files)

Our objective is to configure the Any Cloud module so that Omeka S can store files in the appropriate folder (public ) on our N0C Storage technology.

At the moment, the module displays the message “The module was successfully configured”, but no files are uploaded, and the integration does not seem to work with our storage. Our hosting customer was advised by us to set a “public path” in the configuration, but it is unclear if the module supports this type of path selection.

We would be glad to collaborate with you to:

1- verify if the module can be configured for self-hosted S3 endpoints with distinct public/private paths, or

2- explore potential adjustments to make N0C Storage fully compatible with the module.

Would it be possible to review this together?

Thank you,

Marc-Andre B.
PlanetHoster Support