Entity Pilot

Overview

Entity Pilot provides content-staging for Drupal 8.

Features

• Send content between your Drupal sites in bulk
• Auto-resolution of dependencies
• Two way syncing
• Preview incoming content before importing to avoid unexpected changes
• View a diff of incoming content when a version already exists on the destination site
• Secure - content is encrypted at your site before being sent to Entity Pilot
• Build your own content-repository
• Send content between sites that don't share the same configuration (content-types and fields) - by enabling the Entity Pilot Map Config sub-module.

Requirements

• Dynamic Entity Reference
• php-encryption library - install via composer - see install instructions

Installation overview

• Download and extract the module
• Add the php-encryption library composer require "defuse/php-encryption:~1.2"
• Sign up for an account on Entity Pilot
• Create an Entity Pilot account on each of the sites you need to share content, using the details from when you signed up.
• Start creating departures and arrivals to send and receive your content.
• See the full installation instructions for more details.

Known problems

• Books are not retained (#2698789: Add book module support) because they have no serialization support in core. Core issue: #2698785: Cannot deploy book nodes - book metatdata not serialized
• Paragraphs cannot be deployed because Entity Reference revisions doesn't have serialization support. See #2696447: Paragraph module integration and #2598138: HAL serialization for ERRItem is broken.
• #2710689: Queueing a departure results in fields being excluded by field access - use 'Approve and send' instead

Please use the issue queue to search for any known issues or to add a new one.

Please note that tests can't be run on drupal.org until #2597778: Install composer dependencies for contrib projects before running tests is fixed

Credits

Entity Pilot was written by Lee Rowlands (@larowlan).