I have a bit of an unusual problem that I can't quite work out. For the most part, uSync works fantastically well however occasionally the following occurs.
Dev environment:
VS2015 with Umbraco & uSync installed via nuget
Connect to staging DB
All Umbraco changes made in dev, only content changes in staging.
Bitbucket as Version Control.
uSync/* included in version control & solution.
Staging envrionment:
Azure web app
Continuous deployment from Bitbucket
Connect to staging DB
Prod environment:
Azure web app
No continuous deployment
Connect to prod DB
Uses uSync to deploy Umbraco changes
The situation I just had, was changing a Data Type called "Footer Items" from a Multiple Content Picker to Archetype. I can see the changes made in the staging DB and the uSync files that were saved to disk.
The changes were committed to BitBucket and then merged to our staging branch which is then automatically deployed to Azure.
What I found was that even though the changes were made against the staging DB in my development environment, after the site was loaded in Azure all those changes were reverted and the "Footer Items" data type was back as it was before changing it from a Multiple Content Picker to Archetype.
I looked at the uSync file on Disk (usync/data/DataType/footer-items/FooterItems.config) and it looks correct as per the file I have in dev & in version control.
FWIW: A change to another data type has worked perfectly fine. The above scenario can happy with any change, not just the two data types I mentioned above.
I'm wondering if the scenario we have setup is the correct way to use uSync between our dev/staging environments. It is the same DB so I thought it should be working without issue. I'm also wondering where I can look to further troubleshoot the problem?
Changes reverting on deployment
Hi,
I have a bit of an unusual problem that I can't quite work out. For the most part, uSync works fantastically well however occasionally the following occurs.
Dev environment: VS2015 with Umbraco & uSync installed via nuget Connect to staging DB All Umbraco changes made in dev, only content changes in staging. Bitbucket as Version Control. uSync/* included in version control & solution.
Staging envrionment: Azure web app Continuous deployment from Bitbucket Connect to staging DB
Prod environment: Azure web app No continuous deployment Connect to prod DB Uses uSync to deploy Umbraco changes
The situation I just had, was changing a Data Type called "Footer Items" from a Multiple Content Picker to Archetype. I can see the changes made in the staging DB and the uSync files that were saved to disk.
The changes were committed to BitBucket and then merged to our staging branch which is then automatically deployed to Azure.
What I found was that even though the changes were made against the staging DB in my development environment, after the site was loaded in Azure all those changes were reverted and the "Footer Items" data type was back as it was before changing it from a Multiple Content Picker to Archetype.
I looked at the uSync file on Disk (usync/data/DataType/footer-items/FooterItems.config) and it looks correct as per the file I have in dev & in version control.
FWIW: A change to another data type has worked perfectly fine. The above scenario can happy with any change, not just the two data types I mentioned above.
I'm wondering if the scenario we have setup is the correct way to use uSync between our dev/staging environments. It is the same DB so I thought it should be working without issue. I'm also wondering where I can look to further troubleshoot the problem?
Thanks in advance, David
is working on a reply...