The README in the v2 branch should contain all the information you need to get started.
Please try it out, file issues and submit your feedback!
Note that Caddy 2 is not feature-complete (is lacking some obvious things like logging, the Caddyfile, etc.) but we wanted you all to start getting involved ASAP.
Hey Noam! Yes, we’re working on an enterprise-grade cache module. I have a very basic distributed cache working (neglecting many corner cases currently). It’s still in the early stages. Would you be able to describe more specifically what your requirements are? You can either reply here (most helpful for the community) or email or DM me.
So every request URL will be save in Caddy cache with a tag we will send to Caddy. For example: “12345”.
The object will be use from Caddy cache until he expire or until we use Caddy API to remove this tag: “12345” from the cache.
Important notes for us:
Using the Caddy API we can remove a tag, so in one call we can remove a lot of cache objects.
I think KeyCDN doing that very very good:
They also have option to remove cache by URL:
This solution will help us move most of our traffic to Caddy server and reduce our web servers. Also it will help us to build Caddy server around the world that call main web server.
Let me know if you have more questions about that and keep the great work
Yes, we’re working on an enterprise-grade cache module. I have a very basic distributed cache working (neglecting many corner cases currently). It’s still in the early stages. Would you be able to describe more specifically what your requirements are? You can either reply here (most helpful for the community) or email or DM me.