I am looking to see how other people who have implemented this have dealt with this situation.
We have a staging server where we are developing documents and updating the documents before release--there are about 50 documents. Each document is its own space. For release, we need to move all the documents to the production server which have books with the same name, but older versions. At present, we have download each document/space, export and import them into the new server because Confluence doesn't allow you to overwrite a space with another space of the same name.
This is getting very complicated as we have to do this often. I know there is a CLI which replaces spaces, but that didn't work for us.
I appreciate if anyone who has to deal with a similar situation can reply how they resolved this problem.
The only solution I have is to first delete the space in production that's being replaced before uploading the newer version. Should be quick and painless unless you're needing content from the old space. If you do then move it to a different space first so the spacekey doesn't match the space you're uploading.
Most of us don’t need much convincing that stakeholder management is important. It just makes sense that keeping everyone in-the-know on projects and assigning clearly defined roles is key to having ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs