All geek questions in one place

Getting Excon :: Errors :: SocketError when reading images from one S3 and writing to another?

We have an intermediate server setup to use another S3 bucket from our production server, but this requires that we manually synchronize the images between the buckets in order to see the images on stage. Since we have tens of thousands of images (growing daily), this is not viable.

In any case, to set up Carrierwave to read images from our S3 products, but write any new images to the S3 stage (so as not to pollute our image store)?

UPDATE . I tried to create my own storage engine for CarrierWave that does this (see this method - basically identical to the fog storage engine, except line 228), but I get this error when trying to get images:

Excon::Errors::SocketError (hostname does not match the server certificate (OpenSSL::SSL::SSLError)): lib/carrier_wave/storage/dual_fog.rb:214:in `exists?' lib/carrier_wave/storage/dual_fog.rb:228:in `public_url' lib/carrier_wave/storage/dual_fog.rb:267:in `url'

Does anyone know why this is? As you can see from the code in essence, I want this solution to be able to read from the stage and retreat to production if the image is not found during production. However, all write operations should be performed only at the stage.

+6
source share
1 answer

There are several ways to use S3. If you have points in your bucket and want to do SSL, you need to make your URLs look like this: https://s3.amazonaws.com/staging.asset.domain.com/blah . You cannot use https://yourdomain.com/blah because amazon does not have your certificate. You also cannot use https://staging.asset.domain.com.s3.amazonaws.com/blah , because certificates go only one level. (i.e. if there are no dots in your bucket, this will work.)

+2
source

Source: https://habr.com/ru/post/924584/

More articles:


All Articles