Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a rails app that I’m going to host on engineyard and want to store image files on s3.
But I don’t know if I want all developer machines to beusing s3 for storage of all our test and dev images. Maybe it’s not an issue — but it seems like a waste to have everyone storing all our images in s3.
I’ve heard of some ppl who store images on s3 ‘hacking’ dev environments to store images locally on the file system — and then using s3 in prod only.
What are other people doing?
You could write a wrapper class around the gem that uses the file system for image storage instead of S3 for non-production environments. Then your application would use the wrapper rather than the gem directly. Or make the image store the wrapper uses a configuration option.