Environment: Umbraco v7.1.8 running as an Azure webapp
Has anyone run into the issue where you have an Azure web application (with an active swap site using the same database), where the scheduling of content doesn't work because the swap partition actually does the publish instead of the main environment?
The result is that the website cache of the productionwebsite doesn't contain the newly published page because it's only updated on the swap site. If you look in the backend everything is fine (because of shared db)
from what I see the only solution would be to configure them as 2 load balancing nodes?
Azure web app - Swap site conflict with scheduled content publishing
Environment: Umbraco v7.1.8 running as an Azure webapp
Has anyone run into the issue where you have an Azure web application (with an active swap site using the same database), where the scheduling of content doesn't work because the swap partition actually does the publish instead of the main environment?
The result is that the website cache of the productionwebsite doesn't contain the newly published page because it's only updated on the swap site. If you look in the backend everything is fine (because of shared db)
from what I see the only solution would be to configure them as 2 load balancing nodes?
any ideas/workarounds/alternative solutions?
is working on a reply...