I was willing to use uSync to import doctypes into a cloned repo from Umbraco Cloud but according to Sebastiaan Janseen there are serious conflicts with Courier. His comment here
Do you know if there is a way to avoid those conflicts ? ... perhaps excluding the uSync files from being committed to the Umbraco Cloud Dev environment ? Have you tested this ?
uSync shouldn't run on the Umbraco Cloud - at startup it will detect if you are running on the cloud and will just exit . so leaving the files there shouldn't cause any conflicts.
that said if you pull something down from umbraco cloud, i am not sure if usync would then run - so it's probably best not to have uSync on a cloud project ?
if you do need both, i would suggest turning off usync in the usyncbackoffice.config file (just set import = false) and then it won't try to do anything.
as far as i know just having the usync files there shouldn't cause any issues because nothing will try and do anything with them.
Dave, I'm aware of Courier and I think is working pretty nice after the last updates.
This is our scenario:
I have a local website where I test contributions made by some team members. Once I am ready, I transfer the updates from this local website to the (also local) cloned git repo from the Umbraco Cloud dev environment.
I would like to use uSync to import doctype definitions and dictionary items into my local cloned git repo (from uaas dev).
I think the questions are:
a. Does uSync affects Courier in anyway ?
b. Does Courier detects the new/updated doctypes or dictionary items made by uSync and register them so they are marked for commit to the ucloud dev env.
c. is there any problem if I customize the .gitignore (in my cloned git repo) to exclude usync related files and avoid messing up with the ucloud install.
I can not guarantee that what uSync does fires the correct events and therefore I can not guarantee that Courier will pick up on your changes and create the correct data files. In theory it SHOULD work but it is untested and not recommended.
We have seen data corruption with uSync before which I assume is why it doesn't run on Umbraco Cloud any more.
So.. proceed at your own risk, we (Umbraco) does not recommend working this way, which is also not the way Umbraco Cloud was designed to work.
Not all our team members have access to the ucloud dev env and we have an extra step for QA before pushing changes to the "dev env". This reduces the risk of someone's work affecting others or breaking de dev site completely while there is other funcionality ready for being tested by customer and transfered to live.
What I am trying to do with uSync is to import doctypes and dictionary to my local cloned website and not having to create them manually.
If this is possible with other package or method it would fit our purpose.
You can use feature branches with Umbraco Cloud. As long as you don't merge it to the master branch of your local cloned environment these will not get deployed.
So you can have your teammembers develop in a feature branch. Check that work and then merge to master for deployment.
This way you don't need a extra seperate environment.
In theory you can do what you need to do with uSync / Courier
uSync doesn't do anything with any courier config / actions and as far as
i am aware courier doesn't do anything with usync files or config.
the key is making sure that both don't try and do the same thing or run at the same time on any of your installs, because that's when the fun will start!
based on what you're saying i would have uSync in purely manual mode on you're local site (so import = false, ExportonSave = false, in the usyncbackoffice.config) and pull in any usync changes via the dashboard - so you can see them happen.
if you are then happy with them you could use the other methods to get them to the cloud / live site.
That would reduce the manual creation step , and if everything is turned off inside usync then you shouldn't get any conflicts with courier / deploy.
but i would exercise caution, as you do have two independent deployment systems working on the same site, and it could get messy.
Dave, Kevin, Sebaastian... thanks for all your comments.
I appreciate it very much !!!
I admit our scenario with the extra local site may be complicating things due to our lack of experience with the "feature branches" that Dave just mentioned. We will test your suggestions for sure.
One last question folks:
Is there any other way to export / import doctypes or dictionary items available or planned for Umbraco Cloud ? Why it is possible to export / import doctypes with the standard v7.x but this is not available with the cloud version ?
uSync and Umbraco Cloud
Hi
I was willing to use uSync to import doctypes into a cloned repo from Umbraco Cloud but according to Sebastiaan Janseen there are serious conflicts with Courier. His comment here
Do you know if there is a way to avoid those conflicts ? ... perhaps excluding the uSync files from being committed to the Umbraco Cloud Dev environment ? Have you tested this ?
Thanks in advance for your feedback
Hi
uSync shouldn't run on the Umbraco Cloud - at startup it will detect if you are running on the cloud and will just exit . so leaving the files there shouldn't cause any conflicts.
that said if you pull something down from umbraco cloud, i am not sure if usync would then run - so it's probably best not to have uSync on a cloud project ?
if you do need both, i would suggest turning off usync in the usyncbackoffice.config file (just set import = false) and then it won't try to do anything.
as far as i know just having the usync files there shouldn't cause any issues because nothing will try and do anything with them.
Kevin
Hi Jose,
Like Kevin said uSync should not run on Umbraco Cloud. But more important if you are on Umbraco Cloud you don't need uSync at all.
The deployment engine of Umbraco Cloud, called courier, handles everything uSync does for you.
Dave
Kevin, Dave, thanks for your reply
Dave, I'm aware of Courier and I think is working pretty nice after the last updates.
This is our scenario:
I have a local website where I test contributions made by some team members. Once I am ready, I transfer the updates from this local website to the (also local) cloned git repo from the Umbraco Cloud dev environment. I would like to use uSync to import doctype definitions and dictionary items into my local cloned git repo (from uaas dev).
I think the questions are:
a. Does uSync affects Courier in anyway ?
b. Does Courier detects the new/updated doctypes or dictionary items made by uSync and register them so they are marked for commit to the ucloud dev env.
c. is there any problem if I customize the .gitignore (in my cloned git repo) to exclude usync related files and avoid messing up with the ucloud install.
thanks again to both of you for the help
I can not guarantee that what uSync does fires the correct events and therefore I can not guarantee that Courier will pick up on your changes and create the correct data files. In theory it SHOULD work but it is untested and not recommended.
We have seen data corruption with uSync before which I assume is why it doesn't run on Umbraco Cloud any more.
So.. proceed at your own risk, we (Umbraco) does not recommend working this way, which is also not the way Umbraco Cloud was designed to work.
Hi Jose,
Why are you use a local website and a local cloned website from Umbraco Cloud ? Seems like not a usual setup to me.
Dave
Hi Dave
Not all our team members have access to the ucloud dev env and we have an extra step for QA before pushing changes to the "dev env". This reduces the risk of someone's work affecting others or breaking de dev site completely while there is other funcionality ready for being tested by customer and transfered to live.
What I am trying to do with uSync is to import doctypes and dictionary to my local cloned website and not having to create them manually.
If this is possible with other package or method it would fit our purpose.
jac
Hi Jose,
You can use feature branches with Umbraco Cloud. As long as you don't merge it to the master branch of your local cloned environment these will not get deployed.
So you can have your teammembers develop in a feature branch. Check that work and then merge to master for deployment.
This way you don't need a extra seperate environment.
Dave
Hi Joes
In theory you can do what you need to do with uSync / Courier
uSync doesn't do anything with any courier config / actions and as far as i am aware courier doesn't do anything with usync files or config.
the key is making sure that both don't try and do the same thing or run at the same time on any of your installs, because that's when the fun will start!
based on what you're saying i would have uSync in purely manual mode on you're local site (so import = false, ExportonSave = false, in the usyncbackoffice.config) and pull in any usync changes via the dashboard - so you can see them happen.
if you are then happy with them you could use the other methods to get them to the cloud / live site.
That would reduce the manual creation step , and if everything is turned off inside usync then you shouldn't get any conflicts with courier / deploy.
but i would exercise caution, as you do have two independent deployment systems working on the same site, and it could get messy.
Dave, Kevin, Sebaastian... thanks for all your comments.
I appreciate it very much !!!
I admit our scenario with the extra local site may be complicating things due to our lack of experience with the "feature branches" that Dave just mentioned. We will test your suggestions for sure.
One last question folks:
Is there any other way to export / import doctypes or dictionary items available or planned for Umbraco Cloud ? Why it is possible to export / import doctypes with the standard v7.x but this is not available with the cloud version ?
Best regards
is working on a reply...