CODEWITHSUNDEEP
ruby-on-railsherokuruby-on-rails-4amazon-s3carrierwave
sri_sankl
sri_sankl

Reputation: 243

Carrierwave store images locally not on s3 at heroku

I am using carrier wave to upload images and display them in a photo-gallery. Carrier wave store files at public/uploads. But these images are not getting displayed at heroku. I found that heroku is read only and we should store files at s3.

Is there any other alternatives than s3?If yes, can you please share here?

Upvotes: 1

Views: 990

Answers (1)

Richard Peck
Richard Peck

Reputation: 76784

Heroku is only read only if you're on the bamboo stack (old). For cedar, they use a ephemeral writeable filesystem, which means that whilst you can upload, it gets wiped with every deploy

S3 is not your only option; it's just Amazon's storage system. You've got dropbox, Azure, RackSpace & a bunch of others which provide similar functionality

Your question should really be which storage solution is right for my app?

The main issue is the location of your files -- they need to be close in proximity to your app, to reduce latency. We've had a problem recently hosting S3 files through a Rackspace app - because S3 is not in RackSpace's datacenter, the latency was high

Because Heroku is built on Amazon's AWS cloud, meaning serving assets from S3 the most efficient & logical method to provide your assets

Upvotes: 6

Related Questions