/oe_migration

Primary LanguagePHPEuropean Union Public License 1.2EUPL-1.2

OpenEuropa Migration

Build Status

The OpenEuropa Migration provides extensions to the core migration framework, to migrate data from Drupal 7 to the OpenEuropa project.

Table of contents:

Installation

The recommended way of installing the OpenEuropa Migration module is via Composer.

composer require openeuropa/oe_migration

Enable the module

In order to enable the module in your project run:

./vendor/bin/drush en oe_migration

OpenEuropa Migration

The module provides the following plugins and sub-modules:

Process plugins

  • ApplyFilters (oe_migration_apply_filters) : Applies filters of the given filter format to a string.
  • Pipeline (oe_migration_pipeline) : Executes a group of process plugins, stored in a oe_migration_process_pipeline configuration entity.

Sub-modules

  • OpenEuropa Workflow

    • [Process plugin] SetWorkflowState (oe_migration_set_workflow_state) : Sets the workflow state of an entity.

      Dependencies: Workflows

Development setup

You can build a test site by running the following steps.

  • Install all the composer dependencies:
composer install

  • Customize build settings by copying runner.yml.dist to runner.yml and changing relevant values.

  • Install test site by running:

./vendor/bin/run drupal:site-install

Your test site will be available at ./build.

Please note: project files and directories are symlinked within the test site by using the OpenEuropa Task Runner's Drupal project symlink command.

If you add a new file or directory in the root of the project, you need to re-run drupal:site-setup in order to make sure they are be correctly symlinked.

If you don't want to re-run a full site setup for that, you can simply run:

$ ./vendor/bin/run drupal:symlink-project

Using Docker Compose

Alternatively, you can build a development site using Docker and Docker Compose with the provided configuration.

Docker provides the necessary services and tools such as a web server and a database server to get the site running, regardless of your local host configuration.

Requirements:

Configuration

By default, Docker Compose reads two files, a docker-compose.yml and an optional docker-compose.override.yml file. By convention, the docker-compose.yml contains your base configuration and it's provided by default. The override file, as its name implies, can contain configuration overrides for existing services or entirely new services. If a service is defined in both files, Docker Compose merges the configurations.

Find more information on Docker Compose extension mechanism on the official Docker Compose documentation.

Usage

To start, run:

docker-compose up

It's advised to not daemonize docker-compose so you can turn it off (CTRL+C) quickly when you're done working. However, if you'd like to daemonize it, you have to add the flag -d:

docker-compose up -d

Then:

docker-compose exec web composer install
docker-compose exec web ./vendor/bin/run drupal:site-install

Using default configuration, the development site files should be available in the build directory and the development site should be available at: http://127.0.0.1:8080/build.

Running the tests

To run the grumphp checks:

docker-compose exec web ./vendor/bin/grumphp run

To run the phpunit tests:

docker-compose exec web ./vendor/bin/phpunit

Step debugging

To enable step debugging from the command line, pass the XDEBUG_SESSION environment variable with any value to the container:

docker-compose exec -e XDEBUG_SESSION=1 web <your command>

Please note that, starting from XDebug 3, a connection error message will be outputted in the console if the variable is set but your client is not listening for debugging connections. The error message will cause false negatives for PHPUnit tests.

To initiate step debugging from the browser, set the correct cookie using a browser extension or a bookmarklet like the ones generated at https://www.jetbrains.com/phpstorm/marklets/.

Contributing

Please read the full documentation for details on our code of conduct, and the process for submitting pull requests to us.

Versioning

We use SemVer for versioning. For the available versions, see the tags on this repository.