I had a crazy idea when I should have been sleeping that it would be handy to be able to perform a clear cache operation on the target publishing server when pushing, e.g. large image updates.
That came out of a fear that when a client of mine makes a large set of edits to be pushed at once, users of the site might see some screwy pages until the cache refreshes. I have witnessed this myself updating media via git on command line. I normally have high levels of caching set for production servers.
You could do this by triggering another webhook on the editing instance. It could be a global checkbox on the file selection list UI.
This idea is not very incompatible with another half-baked plan of mine to split this plugin into "pushy-publisher" and "pushy-target".
I had a crazy idea when I should have been sleeping that it would be handy to be able to perform a clear cache operation on the target publishing server when pushing, e.g. large image updates.
That came out of a fear that when a client of mine makes a large set of edits to be pushed at once, users of the site might see some screwy pages until the cache refreshes. I have witnessed this myself updating media via git on command line. I normally have high levels of caching set for production servers.
You could do this by triggering another webhook on the editing instance. It could be a global checkbox on the file selection list UI.
This idea is not very incompatible with another half-baked plan of mine to split this plugin into "pushy-publisher" and "pushy-target".