pycloudinary does not implement Django's storage API

[omerzimp]

The CloudinaryField is not a FileField which makes it harder to upload images with Django.
Creating a custom storage backend is not that hard.
See the documentation for details.

[bufke]

Has anyone started work on this? I was thinking about it. May or may not have the time to do so.

[thedrow]

I don't think anyone has.

[tocker]

@omerzimp, @bufke and @thedrow - We are looking into it.

[klis87]

If anyone still needs Cloudinary storages, I've made a package providing those (both for static and media files) - https://github.com/klis87/django-cloudinary-storage . It also has management commands to clean unnecessary files. I hope you will find it useful.

[shangxiao]

Using the storages api is definitely the "django way" to handle media and should be a priority as it means that it would work well with a lot of other supplied & 3rd party components.

I'm unfortunately forced to add this caveat to recommendations that I give to colleagues & folks on the django irc which is a shame because the platform itself is nice. (Although django-cloudinary-storage does look promising!)

[pfcodes]

+1 really need this. All my projects have a local environment which stores media files on my local file system thanks to the Django Storages API. The Cloudinary image field breaks that.

[tommyg-cld]

@pfcodes can you use https://github.com/klis87/django-cloudinary-storage ?