Adding idrive as S3 service

Do you mean I just need to fill the values demanded by Aws_S3 fields in Disco Admin Settings with the values provided by iDrive S3? (because there are no other fields in the disco admin settings for any other S3 service).

It might be a better choice to declare those values in app.yml instead.

To answer your question, Yes, the settings for S3 are the same regardless of if you’re using amazon or any other S3 compatible service.

2 Likes

I thought it’d be better thru Admin settings, which we can change any time wo needing to rebuild our container. :grinning: :slight_smile:

Great!!

It seems it doesn’t.
When I fill idrive’s S3 values in disco admin settings, it refuses to accept iDrive’s endpoint address:

Pls tell if I’m missing something here? I’ve filled iDrive’s Access Keys and Secret, but can’t test them till this is sorted out.
Also there is no value supplied by iDrive to be filled in S3 Cdn Url

Only needed if idrive actually offers CDN for their storage. Alternatively you can use bunny.net for cdn if needed.

Did you try adding https://

2 Likes

I tried now. But it still gives same ā€˜wrong format’ error.

I noticed that IDrive supports the S3 API according to IDrive documentation, but I haven’t tried using it IDrive as an S3 backup for Discourse.

1 Like

I now noticed that although it accepted the endpoint value NOW with https, but the idrive bucket is still not reachable.

1 Like