Entity Pilot makes it easy to transport your content from one site to another.
How does it work?
Entity Pilot makes the most of improvements in Drupal 8's Entity Field API and the new core serializer module.
Content is grouped together into logical flights, but can be sent as individual items if you have enough capacity in your plan.
Dependencies are auto-detected and added as baggage, ensuring each flight is a distinct group of self-contained entities.
On another site, you setup your Entity Pilot account and then create a new Arrival. This presents you with the list of your flights that exist in Entity Pilot for your account. After selecting the flight for the arrival, you move to the approval stage.
The approval stage presents you with a list of content on the incoming flight. Each item can be previewed and if it matches existing content on the site (see dealing with conflicts) the administrator is able to view a diff of the changes.
Finally, the desired items to import are selected and imported either immediately, or via background processing.
Who is behind Entity Pilot?
Entity Pilot is the brain-child of long-term Drupal contributor Lee Rowlands (larowlan). Drawing on his six-years of experience building and developing sites with Drupal, Entity Pilot builds on real-world pain points encountered with content-deployment. Pain points from both a developer's perspective but also from the perspective of the many clients, of varied backgrounds and sizes, that he has worked with during this time.
Who has access to my content
Only people who have your encryption key. Entity Pilot cannot read or view your content - it is encrypted by your Drupal site before being sent to Entity Pilot and decrypted when received back from Entity Pilot, before importing.
The system was designed with security in mind, as your content might contain sensitive information or in the case of user accounts - private information. So this gives you piece of mind that unless someone has your personal encryption key - known only to you - your content cannot be read.
Drupal 7 backport
We're actively working on a Drupal 7 backport - opening the potential for painless content-staging to the many existing Drupal 7 sites.
What's on the roadmap for the Drupal module? Lots - including:
- Drush integration - so you can create an arrival and land a remote flight during a deploy - import content during a deploy.
- Automatically create a departure containing all terms in a vocabulary - quickly sync whole vocabularies- Available from beta 4
- Schedule an arrival - set a date and time for approved items to be imported.
- Track the source arrival from which content was created, allowing site owners to be notified when the remote flight is updated; and hence a new version of the content exists.
- Automatically create a departure from the content edit form, allowing content to be sent as soon as it is created.
- Views integration for departures and arrivals.
- Map missing config in incoming flights to existing fields and content-types on the destination site
- Create a new departure from an arrival, allowing for faster two-way syncing - Available from beta 5.