Acquia Content Hub attempts to simplify the setup process by removing most of the publishing configuration, ensuring Acquia Content Hub acts like a replication service.
Acquia Content Hub communicates all necessary information to support content syndicated from a publishing website to a subscribing website, by default. Syndicated information includes content bundles, field storage and configuration, view modes, form modes, and other required information.
Getting started
Before you can create a publishing website, you must install and enable the Acquia Content Hub module. After you enable the Acquia Content Hub Publisher module, Acquia Content Hub will add content to your export queue. When any entity in your Drupal website is created or updated, it queues for export to the Acquia Content Hub service.
Prerequisites
Configuring an Acquia Content Hub publisher website requires the following information:
- Acquia Content Hub Hostname: Your Acquia Content Hub service URL.
- API Key: Your Content Hub API key.
- Secret Key: Your Content Hub secret key.
If you don’t have these, see Configuring Content Hub 1.x.
Acquia Content Hub also requires a valid SSL certificate for normal operation.
Note
Websites without a valid SSL certificate must configure their webhooks to use http, not https.
Configuring the publisher
To test content publishing:
- Sign in to your Acquia Content Hub publishing website as a user with the Administrator role.
- In the admin menu, click Extend.
- Select the checkbox next to Acquia Content Hub Publisher, and then click Install.
- In the admin menu, go to Configuration > Acquia Content Hub.
- Enter the following information:
- Acquia Content Hub Hostname: Your Acquia Content Hub service URL.
- API Key: Your Content Hub API key.
- Secret Key: Your Content Hub secret key.
- Client Name: Use a name which describes the publisher website, such as
publisher_dev. Client names should be unique per website and environment and not contain special characters. The Content Hub service uses the client name across websites to distinguish where your content was created. Publicly Accessible URL: The field populates with a default value. Cloud Platform websites will be accessible by default; if you are attempting to install your publisher in an inaccessible location (for example, locally), you may register your website with the service, but the Content Hub service can’t access your website, which will cause errors and prevent some features from working.
Note
The publicly accessible URL must be an externally accessible URL. It can’t be behind a firewall or use password protection such as the Shield module or an
.htaccesspassword. Content Hub must communicate with a subscriber’s website, and receive a valid response from the URL. If you require password protection of a website, you must allowlist the webhook URL path to be publicly accessible.
- Click Register site.
Acquia Content Hub will now register with the Content Hub service. If no errors display, the website has connected.