I there ! So, going on the next step on uSync... I'm currently trying to modify a document type in my local computer, then apply it to staging environment, but here I'm am, stuck again.
Like, for example : I delete uSync folder on my computer, and also on the staging server.
I make a change to a member type, then full export.
So now, I in the membertype def.config, I have those two properties :
When you export on your local machine you are creating files in the uSync folder that contains the definitions for your member types and other types you have selected.
If you then create a new branch and run a build, you should ensure that those uSync files are included in that branch, and that build.
Then on your destination server, you have to import those changes from the the uSync config files.
If this isn't working, then either:
Somehow the uSync files are not in the build - there is something wrong with the build process. I would inspect your build files, to ensure they contain the correct uSync files (with the additional property).
You are overwriting the updated uSync files with data from the staging server. I.e, you are exporting on staging then importing.
What is your sync setting for uSync on staging?
Set it to "Manual Sync"- then manually run the import after the build.
As I checked for now, the changes are correctly included in the branch when I commit the files, and when I deploy the staging environment, it creates the uSync folder containing the uSync .config files.
But still, I don't understand why the files are created but do not match the .config files I comited...
uSync not syncing ?
I there ! So, going on the next step on uSync... I'm currently trying to modify a document type in my local computer, then apply it to staging environment, but here I'm am, stuck again.
Like, for example : I delete uSync folder on my computer, and also on the staging server.
I make a change to a member type, then full export.
So now, I in the membertype def.config, I have those two properties :
I push those changes in my uSyncTest branch, then run a cutom build on staging from this branch.
When it finishes, the uSync folder is created. But in membertype def.config, I have this :
The second property is not here...
umbraco config is as following so member types should be correctly exported right?
Also, the example is for a member type, but the problem is the same for every other document type I try to modify
When you export on your local machine you are creating files in the uSync folder that contains the definitions for your member types and other types you have selected.
If you then create a new branch and run a build, you should ensure that those uSync files are included in that branch, and that build.
Then on your destination server, you have to import those changes from the the uSync config files.
If this isn't working, then either:
Somehow the uSync files are not in the build - there is something wrong with the build process. I would inspect your build files, to ensure they contain the correct uSync files (with the additional property).
You are overwriting the updated uSync files with data from the staging server. I.e, you are exporting on staging then importing.
What is your sync setting for uSync on staging?
Set it to "Manual Sync"- then manually run the import after the build.
Hello @Matt, and thanks for your time.
Config in staging is already set to Manual. :)
As I checked for now, the changes are correctly included in the branch when I commit the files, and when I deploy the staging environment, it creates the uSync folder containing the uSync .config files.
But still, I don't understand why the files are created but do not match the .config files I comited...
Okay, how are you running your builds?
Well, okay, my bad ! I was mistaken, staging confid had been overwritten by some bad comit I made a few days ago.
So everytime I ran a build, the uSync folder was overwritten... Everything works fine now ! Thanks a lot !
is working on a reply...