Configuring for syndication¶

The following example uses three environments: dev, stage and prod with two websites: domaina.com and domainb.com.

For the websites to all work together with Acquia Content Hub, register six clients, one for each environment and website:

• domainacomdev

• domainacomstage

• domainacomprod

• domainbcomdev

• domainbcomstage

• domainbcomprod

You can register all six Acquia Content Hub clients from a single website, if you want to generate the registrations simultaneously, by performing the following steps:

1. Configure the first client using steps 2—4 on the dev domaina.com website, using domainacomdev as the client name, ensuring you save the client name and the generated origin UUID (universally unique identifier) for later.

2. Execute drush ach-disconnect on the website to remove the client name and origin config values.

3. Execute steps 2—4 again, using the client name domainacomstage, ensuring you save the client name and the generated origin UUID.

4. Perform the steps for each of the six client names, saving each client name and origin UUID.

5. When all registrations are complete, add the dev client name and origin (from step 1 in this example) back to the configuration for this website using drush config-set.

6. Ensure all client names and origin UUIDs are added to configuration for your deployment workflow, so deployments don’t cause changes to the registered client for Acquia Content Hub.

Configuring for personalization¶

In this example, here are three environments: dev, stage and prod with one website, domaina.com. To work with Acquia Content Hub, register six clients, one for each environment and website:

• domainacomdev

• domainacomstage

• domainacomprod

You can register all six Acquia Content Hub clients from a single website, if you want to generate the registrations simultaneously, by performing the same procedure described in Configuring for syndication.

Retrieving registered client IDs¶

If you reset one of your Acquia Content Hub installations, or your UUIDs are lost, retrieve the UUIDs with a Drush command. Run the following command from the command line on a server running an application with the current Drupal version that is already connected to Acquia Content Hub:

drush ev '$c = \Drupal::getContainer()->get("acquia_contenthub.acquia_contenthub_subscription");print_r($c->getSettings()->getClients());'