Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
Has anyone had any experiencing in combining uSync with Courier 3?
We are using uSync as part of our automated deployment process and this has worked extremely well.
However, when attempting to use Courier 3 for content editor triggered deployments, we have issues with Courier identifying missing documents types (they do actually exist) and one of two events occurring:
Thoughts most welcome.
PS Courier 2.5 (because it uses document type alias) has no problem.
I would caution the use of both uSync and Courier at the same time, because as you have found, they may not be tracking in the same way :(
the latest version of usync (v3.x versions) track by both internal guid and alias (they look for the key and if it fails go back to the alias) - but i am not 100% sure what Courier is looking for. It is likely that the ids don't match between you're installations and that courier is then not finding things.
but i know the ability to track and match by internal guid ids is improving with every version of umbraco (so in v7.5 it's fairly solid) and usync moves along with that as more and more internal IDs are usable - so your best bet for ever getting this working would be latest umbraco (v7.5.x), latest usync (v3.3) and latest courier.
but in reality both together is probably always going to cause some issues :(
Thanks for the swift reply Kevin, really appreciate it.
Yes that would be my take on this and it means we, on this project, may need to re-think our approach but at least we're aware of the potential issues and hopefully we can mitigate them.
FYI we were using uSync v126.96.36.199 but following an upgrade to v3.3 AND a full export from the Source and subsequent full import on the Target it now appears to be working correctly.
Does this seem likely or even feasible?
We're also currently using uSync on a large project. We would like to keep using uSync because it has been integrated into our CI workflow.
However we would also like to start migrating content from 1 environment to another. Can we keep using uSync for meta data and Courier 3 for only content?
I am not 100% sure if usync and courier 3 will play well together (because i don't use courier much)
in theory they both do the same thing. match items based on the internal GUIDs of the data, but i think Courier (not deploy) is still doing this via the db so i have no idea if it is marking stuff or keeping it's own track of things. (if it's doing this then the answer is almost certainly no - they won't work together)
but it might be worth a try on a test level, because if usync does sync everything in the way Courier expects it to then it would work quite nice i except (it would probably break any commercial courier support you might get from umbraco if you did it mind)
Content wise it really depends what you mean by keeping the content in sync. if the content is part of a deployment then usync.contentedition will do this and keep it part of your CI. if it's a content editor job then yeah you need something like courier. or manual pushing on content files.
I have always stopped short of making usync into this editor / push based thing because that is what Courier does - it doesn't mean it isn't capable ;) once all the underlying bits (like doctypes) are in place, moving the content isn't actually that hard - especially in post 7.4 versions of umbraco.
Thanks for explaining Kevin.
Our plan is to have 2 separate live environments that are hosted in different continents. They have their own db and filesystem and the only thing we want to sync is the content. Since this won't be part of a deployment I don't think we can use uSync for this. Courier should be able to do this. I just hope it won't conflict with uSync.
Hi Jeroen (and Kevin)
We have been using uSync and Courier together for just over a year now and generally speaking successfully.
Initially when we attempted to use and older version of uSync with Courier 3 we experienced some issues with duplication (Courier itself) probably due to issues with GUIDs (Courier 3 works pretty much entirely with GUIDs and NOT aliases). This meant we had to revert to using Courier 2.
However, upgrading to the latest version of Courier 3 and the latest version of uSync has resulted in the combination working well together (touch wood).
We like the combination of being able to use uSync with our CI implementation whilst leaving the content editors to manage content transfer via Courier.
If you've any specific questions please don't hesitate to drop me a line and hopefully we will have an answer as we've been through this in some detail.
Wow this is great news! Thanks Roger. I haven't used Courier before so do you have any do's and don'ts regarding this setup with uSync?
All I would say is that when transferring content attempt to keep the pushes in small manageable chunks rather than trying to push an entire site across - we have experienced some issues with this.
Always look to keep Courier and uSync as up to date as possible because bug fixes etc. are in newer releases rather than to the release you're currently on.
And, above all else, back up your database before any deployment, uSync or Courier, because at least that way you know you can get back should any issues occur.
Nothing else specific between the two that we've found as long as you keep things updated.
I've been doing some experiments with Courier 3, but so far I did not have much success. Here are the steps I've done so far.
After this I tried to add 1 document and I did include dependencies. It added a lot more files and when I tried to run that on qa I just get a blank screen. No success or error message. Did I do something wrong in the above steps?
So far Courier 3 is a bit disappointing because I'm used to Umbraco Cloud and it works much more simple and better there. Also I can't find any documentation about Courier 3. There are some links to video's that just don't work anymore.
Instead of using the revision system I just deployed content from the content tree using right click selecting the Courier option. Now the content is transferred :-).
Write your reply to:
Image will be uploaded when post is submitted