openeuropa/entity_version

This package is abandoned and no longer maintained. The author suggests using the http://drupal.org/project/entity_version package instead.

Entity Version.

1.0.0-beta1 2019-07-09 12:19 UTC

Requires

• php: ^7.1
• drupal/core: ^8.7

Requires (Dev)

• composer/installers: ~1.5
• drupal-composer/drupal-scaffold: ~2.2
• drupal/config_devel: ~1.2
• drush/drush: ~9.0@stable
• openeuropa/code-review: ~1.0.0-beta2
• openeuropa/drupal-core-require-dev: ^8.7
• openeuropa/task-runner: ~1.0.0-beta5
• phpunit/phpunit: ~6.0
• symfony/browser-kit: ~4.3

EUPL-1.2

README

Entity version allows to attach version number to content revisions that help content editors to understand the evolution of the content item. Versions are composed of major, minor and patch numbers that can be changed manually or by third party modules.

The module ships the Entity version workflows sub-module that allows to configure and control version numbers through workflow state transitions.

Development setup

You can build the development site by running the following steps:

• Install the Composer dependencies:

composer install

A post command hook (drupal:site-setup) is triggered automatically after composer install. It will make sure that the necessary symlinks are properly setup in the development site. It will also perform token substitution in development configuration files such as phpunit.xml.dist.

• Install test site by running:

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

The development site web root should be available in the build directory.

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:

• Docker
• Docker Compose

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

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.