Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
It is recommended that you make use of the "Replicator" role that has been generated to do replication. To do this you can either create a new user with that role, or add that role to an existing user. You will need to do this on both of the Drupal sites.
Configuring local Relaxed settings
On both sites, under /admin/config/relaxed/settings, configure the credentials for the replicator user.
RELAXed Web Services provides two permissions:perform push replication and perform pull replication, their scope is to restrict or allow access to the endpoints defined by the module.
perform pull replication
This permission allow the user to get information from the endpoints using the GET and HEAD HTTP methods (if the endpoint support them). All other methods will be denied.
This guide provides documentation for RELAXed Web Services module.
This module provides a generic RESTful API for all content entities. It extends the core REST API with better support for translations, revisions, file attachments, UUID references etc.
The main use case that people think of when using the Deploy module is Drupal to Drupal deployment, when you have one Drupal site and you're deploying content to another Drupal site.
Dependencies
To deploy content between two different sites the RELAXed Web Services module should be enabled and configured.
Take a look here how to configure RELAXed Web Services module.