You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if this is a bug report or a support request. It's not high-priority because we have a work-around that seems to be working.
When we upgraded our customized copy of archipelago-deployment-live by manually merging from esmero/archipelago-deployment-live/1.0.0, which includes the new esmero/cantaloupe-s3:6.0.0-multiarch image, I failed to notice that there were extensive changes to config_storage/iiifconfig/cantaloupe.properties. Remarkably, everything seemed to work fine! Well, except that we saw some errors for certain file formats, which lead us to notice our failure to pull in the new cantaloupe.properties file. So I copied in the 1.0.0 cantaloupe.properties file, and proceeded to add back in our S3Source settings (access_key_id, secret_key, and BasicLookupStrategy.bucket.name).
However, after restarting containers with these changes, all of our iiif file and info.json links are broken. I tried a few changes in the cantaloupe.properties file, including setting it to the stock 1.0.0 version (without our S3Source settings/credentials), and doing the opposite: adding in credentials/config for both S3Source and S3Cache, correcting the AWS region, and a few other things.
None of these changes helped. At the moment, I have reverted to the old cantaloupe.properties file, except I merged in the processor.ManualSelectionStrategy mappings from the new file, and now, as far as I can tell, everything is working fine.
As I think you know, @DiegoPino, we are using AWS S3 for both file storage and iiifcache. If you have any suggestions for settings I might look at in the new cantaloupe.properties file that might get it working for us, that would be great. But, as I said, we have it working, so no urgency.
The text was updated successfully, but these errors were encountered:
Hi @patdunlavey, any chance it's permissions-related? I know I've accidentally skipped these lines from the docs once or twice in some upgrades I've done:
I'm not sure if this is a bug report or a support request. It's not high-priority because we have a work-around that seems to be working.
When we upgraded our customized copy of archipelago-deployment-live by manually merging from esmero/archipelago-deployment-live/1.0.0, which includes the new
esmero/cantaloupe-s3:6.0.0-multiarch
image, I failed to notice that there were extensive changes toconfig_storage/iiifconfig/cantaloupe.properties
. Remarkably, everything seemed to work fine! Well, except that we saw some errors for certain file formats, which lead us to notice our failure to pull in the new cantaloupe.properties file. So I copied in the 1.0.0 cantaloupe.properties file, and proceeded to add back in our S3Source settings (access_key_id, secret_key, and BasicLookupStrategy.bucket.name).However, after restarting containers with these changes, all of our iiif file and info.json links are broken. I tried a few changes in the cantaloupe.properties file, including setting it to the stock 1.0.0 version (without our S3Source settings/credentials), and doing the opposite: adding in credentials/config for both S3Source and S3Cache, correcting the AWS region, and a few other things.
None of these changes helped. At the moment, I have reverted to the old cantaloupe.properties file, except I merged in the processor.ManualSelectionStrategy mappings from the new file, and now, as far as I can tell, everything is working fine.
As I think you know, @DiegoPino, we are using AWS S3 for both file storage and iiifcache. If you have any suggestions for settings I might look at in the new cantaloupe.properties file that might get it working for us, that would be great. But, as I said, we have it working, so no urgency.
The text was updated successfully, but these errors were encountered: