Upload files encoded as base64 to carrierwave.
This small gem can be useful for API's that interact with mobile devices.
This gem requires Ruby 2.0 or higher.
Add the gem to your Gemfile:
gem 'carrierwave-base64'
Also add this if you need mongoid support:
gem "carrierwave-mongoid"
Mount the uploader to your model:
mount_base64_uploader :image, ImageUploader
Now you can also upload files by passing an encoded base64 string to the attribute.
The file extension for the uploaded base64 string is identified automatically using the mime-types gem and content_type
from the uploaded string.
If the required MIME type is not registered, you can add it, using MIME::Types#add:
MIME::Types.add(
MIME::Type.new('application/icml').tap do |type|
type.add_extensions 'icml'
end
)
You can set the file_name
option to a lambda, that will return a filename without an extension, using the model instance:
mount_base64_uploader :image, ImageUploader, file_name: -> (u) { u.username }
[DEPRECATED: Settings this option to a string is deprecated, if you still want to set the filename to a fixed string, wrap it in a Proc] To set the file name for the uploaded files, use the :file_name
option (without extention):
# Deprecated way:
mount_base64_uploader :image, ImageUploader, file_name: 'userpic'
# New way
mount_base64_uploader :image, ImageUploader, file_name: -> { 'userpic' }
The string with the encoded data, should be prefixed with Data URI scheme format.
Keep in mind, that the content type specified in this string, would be used to identified the file extension. So if you have some custom content type uploaded, don't forget to register a Mime Type for it.
data:image/jpeg;base64,(base64 encoded data)
- Fork it ( https://github.com/[my-github-username]/carrierwave-base64/fork )
- Create your feature branch (
git checkout -b my-new-feature
) - Commit your changes (
git commit -am 'Add some feature'
) - Push to the branch (
git push origin my-new-feature
) - Create a new Pull Request