fog

We received an email from AWS that basically says 'S3 is disabling SSLv3 Support, access will be cut-off in 15 days'. They then listed some buckets we have (one in production) that are 'currently accepting request from clients that specify SSLv3'. The full email is here, and other AWS users seem to have received one too: https://gist.github.com/anonymous/4240c8af5208782c144c My question is how do we test for this scenario, and what do we need to do to prepare for this cut-off date? We use Rails 4.1 and the Fog (~> 1.28.0) and right_aws (~> 3.1.0) gems for AWS access and we're on Heroku. Our

I got this error Missing required arguments: aws_access_key_id, aws_secret_access_key . That seems weird because I already added carrierwave.rb in initializers folder. The access/secret key works perfectly when I use aws-sdk CarrierWave.configure do |config| config.fog_credentials = { provider: "AWS", aws_access_key_id: ENV["PUB-KEY"], aws_secret_access_key: ENV["SEC-KEY"] } config.fog_directory = ENV["mybucket"] end Here's what my working one looks like: CarrierWave.configure do |config| config.fog_credentials = { :provider => 'AWS', :aws_access_key_id => ENV['S3_KEY'], :aws_secret_access_key

I am currently programming a little game using canvas. For the game I need some kind of fog which hides the most part of the map and only a small area around the player should be visible. Therfor I use a second canvas to overlay the one where the game takes place and fill it with a gradient (from transparent to black): function drawFog(){ fogc.clearRect(0,0,700,600); // Create gradient var grd=fogc.createRadialGradient(player.getPosX(),player.getPosY(),0,player.getPosX(),player.getPosY(),100); grd.addColorStop(0,"rgba(50,50,50,0)"); grd.addColorStop(1,"black"); // Fill with gradient fogc

I'm using Carrierwave 0.5.3 and Fog to upload images to Amazon-S3. The setup works smoothly when running locally, no errors. But when running on Heroku, uploads fail with this message: 2011-03-31T12:53:46-07:00 app[web.1]: ArgumentError ( is not a recognized storage provider): 2011-03-31T12:53:46-07:00 app[web.1]: app/controllers/useditems_controller.rb:36:in `create' I've got an initializer: # /config/initializers/fog.rb CarrierWave.configure do |config| config.fog_credentials = { :provider => 'AWS', :aws_access_key_id => 'secret', :aws_secret_access_key => 'also secret', :region => 'eu-west

I'm having this problem trying to use S3 services with fog and the Jquery File Upload (https://github.com/blueimp/jQuery-File-Upload) The error Excon::Errors::SocketError (getaddrinfo: nodename nor servname provided, or not known (SocketError)): This occur when i try to call "save" method in the controller. I'm setting carrierwave as follow: config/initializers/carrierwave.rb CarrierWave.configure do |config| config.fog_credentials = { :provider => 'AWS', :aws_access_key_id => 'access_key_here', :aws_secret_access_key => 'secret_key_here', :region => 'eu-east-1' } config.fog_directory =

CarrierWave has amazing documentation, until you need to do it without a model! I have my uploader and fog settings set up, and they all work fine when using the mounted uploader on a model, but now I want to do it without a model. I have this: uploader = CsvUploader.new something = uploader.store!(File.read(file_path)) uploader.retrieve_from_store!(self.file_name) When I call .store! the code runs immediately which is weird since it should take a few seconds to upload the file? Then after I call .retrieve_from_store! the uploader object has all the correct S3 info, like the full urls and

Im trying to upload images to S3 on Ruby on Rails using carrierwave and fog gems, images are uploaded correctly but when I try tu save the model containing information about the image that was just uploaded Im getting this error: Excon::Errors::MovedPermanently in UserController#show app/models/user.rb:46:in `process_image_with_key' app/controllers/user_controller.rb:12:in `show' <Excon::Response:0x007f97846a3c18 @body="<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<Error><Code>PermanentRedirect</Code><Message>The bucket you are attempting to access must be addressed using the specified endpoint