I work in a spot where we have all of our development happening on one network and when we do a release we push all the confluence content up to another network that our customers are able to see in production. Our production wiki is a living wiki whereby customers can comment, add items to the FAQ, etc. We're trying to figure out the best way to migrate our dev documentation up to production and not stomp on any changes that have happened since we pushed the last release from dev.
Confluence Command Line Interface can be used to push updated pages and attachments without losing page history or comments. But if you need to merge updates, you will need some sort of automated or semi-automated diff and merge and you will need to consider whatever that is wiki or 4.x storage format.
Thanks Bob, I'll play with the CLI and see what I can come up with this weekend. I <3 3 way diff merges :banghead:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.