Overview

Remote-space publishing allows you to edit content on a local Confluence Server or Data Center, and then publish it to a remote Confluence Cloud, Server or Data Center instance.

The Comala Workflows - Remote Publishing app must be installed on the source instance to enable remote-space publishing.

Activating remote-space publishing

There are two steps to setting up different-space publishing:

  1. Set-up the remote Confluence instance
  2. Set-up the local Confluence instance
  3. Update your workflow to trigger the publishing process

Remote setup

These steps should be performed on the remote Confluence instance which you plan to publish content to.

First, create the space where content will be published to.

Next, set up a user account and give that user permissions to view, add and delete content in that space. When content is published in to the space, it will appear to be authored and edited by this user.

Local setup

These steps should be performed on the local instance where the content is initially created.  Note that for remote publishing to work the server hosting the local Confluence instance must be able to access the remote instance.

In the space that holds the source content, navigate to: Space Tools → Workflows → Remote Publishing tab

You will see a form to add a configuration:

FieldNotes
NameThe name of this publishing profile
Base URL

The base URL for the remote instance, for example:

https://www.company.com/confluence/

UserThe username of the user you created on remote instance.  Content updates on the remote instance will be carried out by this user account.
Password

The password of that user

If publishing to a cloud Confluence instance you will need to enter an API token here, not the user's password.  An api token can be generated when logged into an Atlassian account here: https://id.atlassian.com/manage/api-tokens

Space KeyThe SPACEKEY of the space to publish in to on the remote Instance

Workflow markup

The publishing is triggered by an action macro, {remotepublish-page}, which must be used in a {trigger}.

For this example, we'll assume you created a profile with name of "remote":

{workflow:name=Different-space Publishing}
   {state:Editing|submit=Review}
   {state}
   {state:Review|approved=Published|rejected=Editing}
      {approval:Review|assignable=true}
   {state}
   {state:Published|final=true|updated=Editing}
   {state}
   {trigger:pagestatechanged|state=Published}
      {remotepublish-page:remote}
   {trigger}
{workflow}

The example markup above based on the example from Same-space publishing, but we've added the {trigger} at the bottom. When the state changes to Published, the trigger is activated and the {remotepublish-page} macro instructs the Comala Workflows - Remote Publishing app to send the published content to the remote space.

Note: The final=true parameter is not necessary for different-space publishing, all the work is done by the {remotepublish-page} macro.

Macros

Examples

See also