pycloudinary does not implement Django's storage API

Open
#37 7 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
django, python
Domain
backend

Research direction

Start with Django's custom file storage documentation linked in the issue, then inspect how CloudinaryField currently integrates with Django. The work is complete when CloudinaryField supports Django's storage API and image uploads can use it as a FileField-compatible storage path; the payload names no repository files or tests.

Written by the indexing model from the issue text.

Description

enhancement

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.

Dominant language
Python
Stars
262
Forks
133
Avg merge
3m
Merged PRs (30d)
1

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cloudinary/pycloudinary

All issues in cloudinary/pycloudinary

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.