Nit right now. That’s an interesting idea, and in theory I could change the Varnish IP to an array and loop through… I’ll talk to my cohort.
OK cool. I wonder if we could define them as an array in wp-config?
I would be extremely interested in this as well. I currently have 5 Varnish instances that need purging at the same time and no means of doing so, short of buying into Enterprise Varnish which is way too expensive
I wonder if W3TC (which also can purge varnish) can do this…
Reverse engineering THAT plugin has been a rabbit hole. O.O
I know that I’m bringing this thread back from the dead, but I was wondering if there have been any advancements in this area? I’ve been using the plugin (and love it) but we are currently expanding out our failover arch to being fully active-active, and one of the key parts is having multiple front end Varnish servers. Nelson_fss added necessary code in his branch, but unfortunately it does not look like his version is being actively maintained. Any chance that his code could be pulled back into the master branch? Or is there any way that I could assist with implementing this into the plugin?
It’s on my (massive) to-do list. It’s not something I’m working on very much yet because I don’t have a way to test it myself and I’m VERY shy about adding in code I don’t use to a plugin I maintain. If it breaks, I end up in a very bad place where I can’t easily/readily diagnose, test, and fix it.
