Webtools integration for OpenEuropa. Webtools are interactive services available to integrate in a website.
Table of contents:
The recommended way of installing the OpenEuropa Webtools module is via Composer.
composer require openeuropa/oe_webtools
In order to enable the module in your project run:
./vendor/bin/drush en oe_webtools
The Webtools module contains a submodule that provides a service for providing analytics information. For more information on how to use and configure this module, check out the module README.
The Webtools module contains a submodule that provides a service for retrieving information about language coverage of entity resources. For more information on how to use and test this module, check out the module README.
The Webtools module contains a submodule that provides a widget which integrates with the Laco service. For more information on how to use and configure this module, check out the module README.
The Webtools module contains a submodule that provides a widget which integrates with the Geocoding service.
If you want to use the Webtools Geocoding service, enable the submodule:
drush en oe_webtools_geocoding
The Webtools module contains a submodule that provides a widget which integrates with the maps service.
The Webtools module contains a submodule that provides a service for providing Cookie Consent Kit. For more information on how to use and configure this module, check out the module README.
The Webtools module contains a submodule that provides webtools widgets as supported media providers.
You can build the test site by running the following steps.
- Install all the composer dependencies:
composer install
-
Customize build settings by copying
runner.yml.dist
torunner.yml
and changing relevant values, like your database credentials. -
Generate configuration files:
./vendor/bin/run drupal:site-setup
- Install the site:
./vendor/bin/run drupal:site-install
Your test site will be available at ./build
.
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.
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 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.
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
To run the behat tests:
docker-compose exec web ./vendor/bin/behat
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.