<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Migrate API on The Russian Lullaby</title><link>https://www.therussianlullaby.dev/tags/migrate-api/</link><description>Recent content in Migrate API on The Russian Lullaby</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Mon, 27 Jul 2020 00:00:00 +0000</lastBuildDate><atom:link href="https://www.therussianlullaby.dev/tags/migrate-api/index.xml" rel="self" type="application/rss+xml"/><item><title>Drupal Migrations (V): Debugging Migrations-II</title><link>https://www.therussianlullaby.dev/blog/drupal-migrations-five-debugging-migrations-ii/</link><pubDate>Mon, 27 Jul 2020 00:00:00 +0000</pubDate><guid>https://www.therussianlullaby.dev/blog/drupal-migrations-five-debugging-migrations-ii/</guid><description>&lt;p>Following the previous post, in this article I wanted to share again some guidelines for debugging Drupal Migrations. While in the last article I wrote down some questions about modules, plugins and configuration object management, in this case I felt like stopping at something more &amp;ldquo;code-oriented&amp;rdquo;, more specific. I have chosen for this article some guidelines to configure Xdebug in an IDE (in this case I have used PhpStorm) for migrations running in a locally deployed Drupal using DDEV. With the aim of debugging a Migration process -although actually the process is similar for any …&lt;/p></description></item><item><title>Drupal Migrations (IV): Debugging Migrations-I</title><link>https://www.therussianlullaby.dev/blog/drupal-migrations-four-debugging-migrations-i/</link><pubDate>Mon, 29 Jun 2020 00:00:00 +0000</pubDate><guid>https://www.therussianlullaby.dev/blog/drupal-migrations-four-debugging-migrations-i/</guid><description>&lt;p>The Drupal migrations, despite their linearity in terms of definitions, contain a lot of inherited complexity. The reason is very intuitive: although the Migrate API is a supersystem that offers a very simple &amp;ldquo;interface&amp;rdquo; of interactions for the user-developer who wants to build migration processes, in reality several subsystems work by interacting with each other throughout a migration process: Entities, Database, Plugins&amp;hellip;There are a lot of classes involved in even the simplest migration process. If we add the irrefutable fact that a migration will tend to generate errors in …&lt;/p></description></item><item><title>Drupal Migrations (III): Migrating from Google Spreadsheet</title><link>https://www.therussianlullaby.dev/blog/drupal-migrations-three-migrating-from-google-spreadsheet/</link><pubDate>Wed, 27 May 2020 00:00:00 +0000</pubDate><guid>https://www.therussianlullaby.dev/blog/drupal-migrations-three-migrating-from-google-spreadsheet/</guid><description>&lt;p>The systems and subsystems related to Drupal&amp;rsquo;s migration API are certainly exciting. In the previous articles in this series, I wanted to draw as complete a map as possible (part one) of the vast amount of resources, possibilities and referenced experts. In the second part I wanted to expose some basic mechanics of the migration processes in Drupal and knowing that this opens the door to thousands of options, possibilities and techniques&amp;hellip;.I didn&amp;rsquo;t want to let a third article go by without sharing some experiences migrating data from a common format as a Google Spreadsheet, …&lt;/p></description></item><item><title>Drupal Migrations (II): Examples</title><link>https://www.therussianlullaby.dev/blog/drupal-migrations-two-examples/</link><pubDate>Tue, 17 Mar 2020 00:00:00 +0000</pubDate><guid>https://www.therussianlullaby.dev/blog/drupal-migrations-two-examples/</guid><description>&lt;p>As I said in the previous post, during these months I will be playing with migrations and preparing a few cases for a future book, I hope. During these days of confinement, I want to keep publishing small articles here to share migration-related experiences.&lt;/p>
&lt;p>In the previous post, I wrote about Drupal migrations from a toolbox point of view: a set of basic resources to help frame a migration.&lt;/p>
&lt;p>There is a lot of information to process, and of course there are more concepts, techniques, and tactics involved in solving a migration. So this month I want to write something that lets me play with …&lt;/p></description></item><item><title>Drupal Migrations (I): Basic Resources</title><link>https://www.therussianlullaby.dev/blog/drupal-migrations-one-basic-resources/</link><pubDate>Tue, 25 Feb 2020 00:00:00 +0000</pubDate><guid>https://www.therussianlullaby.dev/blog/drupal-migrations-one-basic-resources/</guid><description>&lt;p>I am working on notes for a draft that should become a book about migration
processes built with Drupal and its Migrate API. It is expected to be released
in June 2020, and collecting, testing, and shaping the content has become quite
a large piece of work.&lt;/p>
&lt;p>There are still a few months left before launch, so, to preserve a little
mental health and give these tasks some partial meaning, I thought I could
publish a few small posts here, based on those working notes.&lt;/p>
&lt;p>That way I can share something useful alongside the complementary notes and, if
COVID-19 gets me before the book comes out, at …&lt;/p></description></item></channel></rss>