Remote-space publishing
Overview
Remote-space publishing lets you edit content on a local Confluence instance and then publish it to a remote Confluence Cloud or other hosted Confluence instance.
The Comala Remote Publishing app is used to publish content in a source space to a space in a completely separate instance.
Whenever content is updated and approved in the source instance using Comala Document Management, the Comala Remote Publishing app can automatically update the published content in the remote instance.
The remote instance can be configured to allow anonymous access to share the content with outside users.
 | The Comala Remote Publishing app for Comala Document Management must be installed on the source instance to enable remote-space publishing. The Comala Remote Publishing app only functions when used with Comala Document Management. |
Activating remote-space publishing
Once the Comala Remote Publishing app is installed, there are three steps to setting up different-space publishing:
Set up the remote Confluence instance
Set up the local Confluence instance
Update your applied Comala Document Management workflow to trigger the publishing process
The publishing action in the workflow is actioned using one of the following remote publishing macros.
remotepublish-page to publish a page to the remote instance
remoteremove-page to unpublish (remove) a published page from the remote instance
These publishing action macros are added to workflow triggers in your custom workflow.
Remote instance setup
These steps should be performed on the remote Confluence instance to which you plan to publish content:
Create the space where you want to publish the content
Set up a user account with user permissions to view, add, and delete content in the space for the published content
For Confluence v8.7.1 and later in your source instance, the remote instance must be added to the Confluence Allowlist Configuration with the “Domain Name” type to ensure that outgoing connections to it are accepted (Comala Remote Publishing v2.6.10+).
When content is published into this remote space, it appears to be authored and edited by the user you have set up.
The remote instance can be a server, data center, or cloud instance.
If a Cloud instance is used for the remote instance, then you need to configure an API token in the user account Atlassian administration.
Make sure the API token needed for the user password field is requested by the user who will appear to publish the articles.
Local setup
For remote publishing to work, the server/data center hosting the local Confluence instance must be able to access the remote instance.
These configuration steps are undertaken in each space in the local instance (source instance) where the content is initially created.
Each remote space instance can only be configured as a remote space for a single source space instance.
Source space Remote Publishing dashboard
The remote space details are configured in the Document Management dashboard in the source space that holds the source content.
navigate to Space Tools > Document Management > Remote Publishing
Confluence Allowlist configuration
For a source instance installation of Confluence v8.7.1 or higher, in order for outgoing connections to the remote space to be accepted, you must include the remote instance in the Confluence Allowlist Configuration with the “Domain Name” type.
Add remote space details
Add the remote space details to configure the remote space publishing
Configuration options | Description |
|---|---|
Name | The name of this publishing profile |
Base URL | The base URL for the remote instance, for example
|
User | The username of the user you created on the remote instance
|
Password | The password of the user created on the remote instance - added as User in this configuration 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 Key | The SPACEKEY of the space to publish in to on the remote Instance |
We recommend you set up a user on the remote instance that only has access to the spaces you are publishing to for security purposes. This will also help to prevent any accidental overwrite of other spaces.
Publishing content
In our example, pages and blogposts with an applied Comala Document Management workflow, are published to the remote instance when the page transitions to the Published state.
This is done using the following workflow trigger listening for the state change to the Published state.
{trigger:statechanged|state=Published|queue=true}
{remotepublish-page:remote}
{trigger}
The remotepublish-page macro is configured to publish to the named space, remote.
Publishing requires connection and transmitting data to the other instance, and this could take some time.
As we want to minimize any chance of error or session expiration we queue the request by adding the queue=true parameter to each publishing trigger in the applied workflow.
A pending message is shown when the page is submitted for publishing.
If a published page is updated in the source space, the workflow status is changed in our applied workflow to a different workflow state. This does not affect the remote instance space page.
To publish any updates to the remote instance space the page needs to be re-approved and transition to the workflow state configured in the workflow trigger (the Published state in our example)
Comala Remote Publishing does not add a publishing status breadcrumb to either the source instance space page or the remote instance space page. Management of the published page is based on the applied workflow state and the action of the workflow remote publishing trigger.
Publishing all pages in the Space
If you want all the existing pages in the space to be published remotely, then you need to set the state of all pages to the Published state.
Need support? Create a request with our support team.