1. is it true that all transferred content isn't published?
2. Is it possible to perform a "get latest content" from a production server to the staging environments ? (to synchorize your staging environment with the live where content keeps getting updated)
3. Can it transfer stylesheets, masterpages and documenttypes ? (i don't see any context menu's there)
4. is there any proper documentation anywhere?
5. How does it handle multiple staging environments ? will they continue to overwrite eachothers changes or is there some kind of protective mechanism installed here?
1) Yes, that's true. However this will be an option in Courier 1.2 which is in beta test atm
2) No, currently that's not possible
3) No, Courier can only sync content and media (however it does verify all dependencies before it transfers and tells you if there's any differences and how to solve them)
4) On the PRO download page there's a install and configuration guide
5) Multiple staging environments? For load balancing Courier only transfer data to one server, however Umbracos build-in load-balancing will ensure cache syncing afterwards.
So in fact the courier does not synchonize any changes to masterpages, stylesheets, datatypes, javascript files, images stored outside of the media folder, ...
that's a shame... we would have loved to use this tool but now i don't really see the point... content managers use admin.website.com and all updates are transferred to the loadbalanced server, but we have no way to automate the transfer of changes to the website design (all files mentioned above) from a staging environment to the live environment...
There's quite a number of bigger companies who wants to manage their content from within the firewall and push the content to the live site. There can be a good number of reasons to do it this way (it's *very* secure and you have full preview of how the site will look before you publish, etc.).
Sorry, not to hijack this thread, but I had similar questions with regards to the OP.
On Umbraco's website, they claim "By the touch of a button different instances of umbraco can be sync'ed
whether it be launching a whole new site, getting the latest content to
your development environment or adding new functionality to a staging
server."
What Niels is saying seems to contradict this statement? -- Specifically the parts about getting latest content to your development environment (similar to question #2) and adding new functionality to a staging server (similar to question #3).
Courier is included with every Umbraco Pro subscription. With Courier, moving between development, testing and production environments is a breeze.
Create, preview, and assure the quality of your content in a safe environment behind the firewall and then securely transfer it to your production environment at the proper time. All done by dragging and dropping nodes in the umbraco UI. No programming skills required. Courier for Content ensures that all associated links and media get
transferred as well, and that internal links are updated and functional.
So in fact, if you read very carefully you notice that it's only covering content. This could be writting more explicitly though, it's quite misleading... paying 800€ for rebranding rights is a reasonabe price, but the extra tools you get are nice but not so versatile as is made to believe...
We'll update so it's more clear what the current version does. The latter one is a left over from features we had to pull (and horribly outdated text anyways).
"but the extra tools you get are nice but not so versatile as is made to believe..." That's a very bold statement. Luckily our customers doesn't agree ;-)
It's all a matter of what you expect i guess... I was hoping that we would be able to make any changes on a staging environment (new datatypes, page templates and content using these, or new xslt macro's etc) and then push these to a live environment after testen. After taking a closer look the current version only seems to offer content migration and alerts about incompatibility...quite a difference
Well , after read this issues and several other posts, can somebody explain to me how should work a CLEAN dev,test, deploy process with umbraco?, remember that we have new content in production that I do not have it in development; I just want to know the work around the problem so I can proceed with serious development with umbraco.
There is no automated process to do this... I suggest manually using a tool like "beyond compare" to find the differences between files on your local machine, staging and production...
Alternatively it might be possible to create packages of all code changes?
How this easily incoorporates database changes from staging to live is another matter, that is covered nowhere...
For content you could use contour, or a sql backup... since contour only gives you warnings and doesn't facilitate the creating of document type changes etc....
Some beginners questions about courier
1. is it true that all transferred content isn't published?
2. Is it possible to perform a "get latest content" from a production server to the staging environments ? (to synchorize your staging environment with the live where content keeps getting updated)
3. Can it transfer stylesheets, masterpages and documenttypes ? (i don't see any context menu's there)
4. is there any proper documentation anywhere?
5. How does it handle multiple staging environments ? will they continue to overwrite eachothers changes or is there some kind of protective mechanism installed here?
Good questions!
1) Yes, that's true. However this will be an option in Courier 1.2 which is in beta test atm
2) No, currently that's not possible
3) No, Courier can only sync content and media (however it does verify all dependencies before it transfers and tells you if there's any differences and how to solve them)
4) On the PRO download page there's a install and configuration guide
5) Multiple staging environments? For load balancing Courier only transfer data to one server, however Umbracos build-in load-balancing will ensure cache syncing afterwards.
Hope this helps!
Best,
Niels...
So in fact the courier does not synchonize any changes to masterpages, stylesheets, datatypes, javascript files, images stored outside of the media folder, ...
that's a shame... we would have loved to use this tool but now i don't really see the point... content managers use admin.website.com and all updates are transferred to the loadbalanced server, but we have no way to automate the transfer of changes to the website design (all files mentioned above) from a staging environment to the live environment...
That's correct. It'll change though ;)
> i don't really see the point
There's quite a number of bigger companies who wants to manage their content from within the firewall and push the content to the live site. There can be a good number of reasons to do it this way (it's *very* secure and you have full preview of how the site will look before you publish, etc.).
Sorry, not to hijack this thread, but I had similar questions with regards to the OP.
On Umbraco's website, they claim "By the touch of a button different instances of umbraco can be sync'ed whether it be launching a whole new site, getting the latest content to your development environment or adding new functionality to a staging server."
What Niels is saying seems to contradict this statement? -- Specifically the parts about getting latest content to your development environment (similar to question #2) and adding new functionality to a staging server (similar to question #3).
Can anyone confirm?
Courier is described as
So in fact, if you read very carefully you notice that it's only covering content. This could be writting more explicitly though, it's quite misleading... paying 800€ for rebranding rights is a reasonabe price, but the extra tools you get are nice but not so versatile as is made to believe...
This page needs an urgen update and featureset description though: http://umbraco.org/products/umbraco-courier
You're right!
We'll update so it's more clear what the current version does. The latter one is a left over from features we had to pull (and horribly outdated text anyways).
"but the extra tools you get are nice but not so versatile as is made to believe..."
That's a very bold statement. Luckily our customers doesn't agree ;-)
It's all a matter of what you expect i guess... I was hoping that we would be able to make any changes on a staging environment (new datatypes, page templates and content using these, or new xslt macro's etc) and then push these to a live environment after testen. After taking a closer look the current version only seems to offer content migration and alerts about incompatibility...quite a difference
I am a customer :p
Better update it to "most" then :-)
If you want a refund, just send me an email.
;)
nevermind the refund, i'll be needing 4 more licenses for other sites this and next month
Well , after read this issues and several other posts, can somebody explain to me how should work a CLEAN dev,test, deploy process with umbraco?, remember that we have new content in production that I do not have it in development; I just want to know the work around the problem so I can proceed with serious development with umbraco.
Thank you.
There is no automated process to do this... I suggest manually using a tool like "beyond compare" to find the differences between files on your local machine, staging and production...
Alternatively it might be possible to create packages of all code changes?
How this easily incoorporates database changes from staging to live is another matter, that is covered nowhere...
For content you could use contour, or a sql backup... since contour only gives you warnings and doesn't facilitate the creating of document type changes etc....
Does anybody know if it is in the works to allow you to be able to transfer other things beside media and content?
Being able to transfer Macros, XSLT, and Templates would make this so much better.
-dw
I doubt this is in the running...
is working on a reply...