mirror of
https://github.com/CaddyBuilds/caddy-cloudflare.git
synced 2026-04-26 12:35:55 +03:00
[GH-ISSUE #19] Request for cloudflare + cache-handler #9
Labels
No labels
documentation
pull-request
question
stale
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/caddy-cloudflare#9
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @nodesocket on GitHub (Jun 12, 2025).
Original GitHub issue: https://github.com/CaddyBuilds/caddy-cloudflare/issues/19
Thanks for created/hosting these pre-built images. Anyway to get a
cloudflare+caddyserver/cache-handlerimage? That would be amazing.@vkartk commented on GitHub (Jun 18, 2025):
Hey, @nodesocket thanks! Really appreciate the kind words 🙌
Right now, I’m keeping the pre-built images simple. just Cloudflare for now to keep things lightweight and maintainable.
But the good news is: you can absolutely build your own image with
cache-handlersupport, andit’s designed to be super easy.
Here’s the guide you’ll want to follow:
🔧 https://github.com/CaddyBuilds/caddy-cloudflare?tab=readme-ov-file#building-your-own-docker-image
If you fork the repo, I recommend giving it a more descriptive name (since image names are based on the repo name). Something like:
caddy-cloudflare-cacheor
caddy-cacheflare(just for fun 😄)Then in both
DockerfileandDockerfile.alpine, after this line:just add:
So you’ll end up with:
Follow the rest of the "Build your own image" steps, and you’ll have a custom Caddy image with exactly what you need.
Let me know if you hit any bumps. Happy to help!
@nodesocket commented on GitHub (Jun 30, 2025):
@vkartk thanks for the detailed instructions. Anyway to limit the arch and distribution builds? I really only need linux
amd64and linuxarm64?@nodesocket commented on GitHub (Jun 30, 2025):
Humm, I triggered a GitHub action of
build and pushand it's been running for over 20 minutes. Is that expected?@vkartk commented on GitHub (Jun 30, 2025):
Yep, totally normal. Building all arch/platforms can take 45–60 min, so 20+ min isn’t unusual.
Right now you’d need to edit:
.github/workflows/build-docker-image-alpine.yml.github/workflows/build-docker-image-standard.ymlscripts/check_caddy_status.pyto limit it to just
linux/amd64andlinux/arm64.Good news: I’ll push an update soon so you can control platforms via GitHub vars much easier! 🚀
@nodesocket commented on GitHub (Jun 30, 2025):
@vkartk ok cool. I restarted the GitHub action and sitting at
1h and 5m, but think it's stalled. Has not moved in a very long time.@github-actions[bot] commented on GitHub (Jul 30, 2025):
This issue has been automatically marked as stale due to inactivity. If no further activity occurs, it will be closed in 7 days.