We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Although the file_size_validator looks very clean, if I'm using a single uploader, maybe something as simple as a custom validator would suffice. This highlights the fact that the file size is actually part of the carrierwave object & can be used for custom validations. Here, I demonstrate a use case where the file size is dynamic depending on the user model.
Created "Saving Content Type"
Updated How to: Easy Ajax file uploads with Remotipart (markdown)
Updated Home (textile)
Created How to: Easy Ajax file uploads with Remotipart (markdown)
fix highlight
.dmg file content_type is application/x-apple-diskimage, include 'image', but file is not a image
fixes spelling of "directories"
fog_host has been renamed to assets_host https://github.com/DouweM/carrierwave/commit/7046c93d6b23cffef9f171a5f7f0dd14267a7057
You should use Rack::Test::UploadedFile because strong_parameters won't pass File type.
Use more generic technique to get uploader's file
carrierwave-viewer add-on added
Add carrierwave-imageoptimizer reference
Add carrierwave-sdk add-on link
Need to include `root` here otherwise path is relative and probably incorrect.
#1013 resolves remote_url issue
colons are valid in the path; simplify language
document remote_url difficulties with certain characters
`fog_host` has been changed to `asset_host`
added carrierwave-serializable plugin
Updated How to: Define different storage configuration for each Uploader. (markdown)
Updated How to: Make Carrierwave work on Heroku (markdown)
Didn't know where to put `before :cache`
changed the filename method in PhotoUploader to actually return the random filename. Got rid of @filename ||=
And of course removed the wrong one. Fixed!