We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
enabled ruby syntax for second code block
fix NameError
Updated How to: Make Carrierwave work on Heroku (markdown)
Updated How to: Store the uploaded file size and content type (markdown)
First version
Included new How To on how to keep files on nested edits
Included config.root change initializer as option
Updated How to: Create random and unique filenames for all versioned files (markdown)
Fix typo
Updated Home (textile)
Add carrierwave-dropbox
Created How to: prevent carrierwave from locking the db row of your object while it's processing the image attached to that object (markdown)
the method is fog_directory= not fog_bucket=
Add carrierwave-webdav
Updated How to: ensure file uniqueness. (markdown)
Destroyed How to ensure file uniqueness (markdown)
Updated How to: Cleanup after your Rspec tests (markdown)
Reset secure token to bust browser image caching
Add link to Hacker Notes page for carrierwave
Add issue when using recreate_versions! and unique filenames
Remove unverified note stating using instance variables is unreliable.
Clearly state how unique SecureRandom.uuid is and add gotcha to recreate_versions!
Added one line for people who use carrierwave_backgrounder, I've put it here because it's first result when searching for `recreate_versions!`
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)