🔦 Feature: Add generic s3 compatible storage (e.g. iDrive e2)

cbertelli commented 1 week ago

Please confirm that the feature request does not already exist

[X] I confirm there is no existing issue for this feature request.

Use case

We use iDrive e2 which is compatible with AWS S3, but we cannot enable it as a storage because no integration lets us state the provider but only the bucket name

Additional context

No response

salim-b commented 5 days ago

Generic S3 storage provider support should work in recent versions of NocoDB, cf. https://github.com/nocodb/nocodb/issues/7903.

You should be able to configure object storage via environment variables or via the GUI (relative URL /dashboard/#/account/setup/storage) by choosing the S3 plugin.

cbertelli commented 4 days ago

Thank you, I did not suppose it was generic. Anyway I get an "Invalid URL" error. It may be that I fill the interface with the wrong info. Bucket Name should be filled with the name I gave to the bucket, say "photos" or it should be something like "photos.b6r8.fra5.idrivee2-91.com"? Region can be filled with the name of the region ("Frankfurt") or it is a URL? Endpoint should be the endpoint of the bucket (say " photos.b6r8.fra5.idrivee2-91.com") or it should be the general endpoint address (say "b6r8.fra5.idrivee2-91.com")? Access Control Lists (ACL) may be empty? I have no ACL in my bucket. It is the "name" of the access key? TIA

On Fri, Nov 22, 2024 at 3:14 PM Salim B @.***> wrote:

Generic S3 storage provider support should work in recent versions of NocoDB, cf. #7903 https://github.com/nocodb/nocodb/issues/7903.

You should be able to configure object storage via environment variables https://docs.nocodb.com/getting-started/self-hosted/environment-variables/#storage or via the GUI (relative URL /dashboard/#/account/setup/storage) by choosing the S3 plugin.

— Reply to this email directly, view it on GitHub https://github.com/nocodb/nocodb/issues/9865#issuecomment-2493861229, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACFBXRHWH24PZCORRSNRNZ32B433FAVCNFSM6AAAAABSD6RBRKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJTHA3DCMRSHE . You are receiving this because you authored the thread.Message ID: @.***>

salim-b commented 4 days ago

Bucket name is just the bucket name.
Region is the region identifier (part of the endpoint URL). But region is actually ignored if endpoint is set, the UX/UI could be improved here, see https://github.com/nocodb/nocodb/pull/9053.
ACL only supports canned ACL keywords, I think. But I'm not certain. @DarkPhoenix2704 worked on ACLs, maybe they can shed some light on the details here.

The following settings work for me with Backblaze B2, maybe it helps:

Screenshot from 2024-11-23 15-25-23

cbertelli commented 4 days ago

It worked. I just added "https://" before the endpoint, changed Region with the proper part of the endpoint URL, and added the ACL from this table: https://docs.aws.amazon.com/AmazonS3/latest/userguide/acl-overview.html#permissions Thank you

On Sat, Nov 23, 2024 at 3:36 PM Salim B @.***> wrote:

Bucket name is just the bucket name.

Region is the region identifier (part of the endpoint URL). But region is actually ignored if endpoint is set, the UX/UI could be improved here, see #9053 https://github.com/nocodb/nocodb/pull/9053.

ACL only supports canned ACL https://docs.aws.amazon.com/AmazonS3/latest/userguide/acl-overview.html#canned-acl keywords, I think. But I'm not certain. @DarkPhoenix2704 https://github.com/DarkPhoenix2704 worked on ACLs, maybe they can shed some light on the details here.

The following settings work for me with Backblaze B2, maybe it helps:

Screenshot.from.2024-11-23.15-25-23.png (view on web) https://github.com/user-attachments/assets/55f7edcd-8712-460a-bc4c-5554ec72b6f6

— Reply to this email directly, view it on GitHub https://github.com/nocodb/nocodb/issues/9865#issuecomment-2495499525, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACFBXRACTSDQJ2676IP7ZJ32CCHGTAVCNFSM6AAAAABSD6RBRKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJVGQ4TSNJSGU . You are receiving this because you authored the thread.Message ID: @.***>

nocodb / nocodb