This module provides editorial features for the OpenEuropa project.
Support for Drupal 10 will be added only in 2.x releases.
In 2.x, the support to Poetry has been dropped. In order to upgrade from 1.x to 2.x:
- uninstall
oe_editorial_corporate_workflow_translation_poetry; - upgrade to a 2.x release.
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.
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.
To start, run:
docker-compose upIt'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 -dThen:
docker-compose exec web composer install
docker-compose exec web ./vendor/bin/run drupal:site-installUsing 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.
To run the grumphp checks:
docker-compose exec web ./vendor/bin/grumphp runTo run the phpunit tests:
docker-compose exec web ./vendor/bin/phpunitTo run the behat tests:
docker-compose exec web ./vendor/bin/behatTo 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/.
Please read the full documentation for details on our code of conduct, and the process for submitting pull requests to us.
We use SemVer for versioning. For the available versions, see the tags on this repository.