We have our Umbraco websites set up in a distributed environment. One front end Umbraco instance and one backend Umbraco instance.
This is all working fine, except when it comes to future publishing (i.e. Publish At in the future). The kick off for this can occur on either the front end instance, or the back, which means that both instances need the distributed call config BUT does that mean that there will be a continuous publish loop? i.e. One instance publishes to the other, which in-turn tries to publish to the first, etc?
Distributed calls and Publish At
Hi,
We have our Umbraco websites set up in a distributed environment. One front end Umbraco instance and one backend Umbraco instance.
This is all working fine, except when it comes to future publishing (i.e. Publish At in the future). The kick off for this can occur on either the front end instance, or the back, which means that both instances need the distributed call config BUT does that mean that there will be a continuous publish loop? i.e. One instance publishes to the other, which in-turn tries to publish to the first, etc?
Cheers
is working on a reply...