replacing Images
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
First check whether users are seeing stale images after replacements, especially Creator images or brand emblems; the issue presents cache purging as conditional on this becoming a problem. Read the Cloudflare cache purge API documentation linked in the issue and trace the image replacement and image-cache paths. Done would mean agreeing on when purging is needed and implementing and verifying it for those cases; the issue does not name files or tests.
Written by the indexing model from the issue text.
Description
When replacing images, the cache at Cloudflare keeps these for a bit longer, be it the full file, be it the processed versions via imagekit in the image-cache.
We could purge the Cloudflare cache for these occasions, if it becomes an issue noticed by users, e.g. when updating Creator images, or brand emblems.
https://developers.cloudflare.com/api/python/resources/cache/methods/purge/
import os
from cloudflare import Cloudflare
client = Cloudflare(
api_email=os.environ.get("CLOUDFLARE_EMAIL"), # This is the default and can be omitted
api_key=os.environ.get("CLOUDFLARE_API_KEY"), # This is the default and can be omitted
)
response = client.cache.purge(
zone_id="zone_id",
)
print(response.id)
- Dominant language
- Python
- Stars
- 122
- Forks
- 36
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 28
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from GrandComicsDatabase/gcd-django
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
GrandComicsDatabase/gcd-django#859 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
GrandComicsDatabase/gcd-django#881 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
GrandComicsDatabase/gcd-django#880 · 2 comments ·
Maintainers usually reply within 1 day
-
update django-autocomplete-light, or replacePossibly taken @jochengcd claimed this 3 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 43/100
GrandComicsDatabase/gcd-django#803 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
GrandComicsDatabase/gcd-django#802 ·
Maintainers usually reply within 1 day
All issues in GrandComicsDatabase/gcd-django
Similar issues
-
documentation good first issue priority: P2 status: ready
Difficulty 1/5 Under an hour Newbie friendliness 88/100
RhinoLink-Tech/data-fabric#500 ·
Maintainers usually reply within 1 day
-
backlog
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EchoTools/nevr-runtime#2384 ·
Maintainers usually reply within 1 day
-
[Bug]: The H2 series' and the H3C's fan 3 is labelled "Chamber Fan", Bambu calls it the exhaust fanOpenarea:ui
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
btclib-org/btclib#3062 ·
Maintainers usually reply within 1 day
-
area:evals area:infra enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
jse-avl/support-bot#4 · 1 comment ·