Biblo.dk lukkede den 31. december 2019
This is the administration interface for biblo.dk based on Drupal 8.
The project structure is based on drupal-composer/drupal-project
.
composer install
docker-compose build
docker-compose up
docker-compose run web drush cim -y
example.docker-compose.override.yml
to docker-compose.override.yml
and fill out the required enviroment variables.Third party dependencies are maintained using Composer and declared in composer.json
. This includes Drupal Core, modules and themes from drupal.org as well as third party libraries.
To update dependencies do the following;
composer update
. This will check for updates to all direct and indirect dependencies within the boundaries defined in composer.json
and apply them to the local project.composer.lock
file. This will ensure that the updated versions are used on external environments when running composer.install
.To only update a specific dependency then go through steps 1-3 but run composer update [dependency]
. Example: To update Drupal Core run composer update drupal/core
.
To apply a patch to a dependency do the following:
composer.json
under extra.patches.[dependency-name]
composer update --lock
composer.json
and composer.lock
filesThis project includes a PHP webservice client for accessing the community service.
To update this client do the following:
docker-compose build --no-cache service
swagger-codegen
composer docker-swagger-generate
lib/client
to ensure that new files are owned by the current user.If you do not want to run the community client locally using Docker and you have access to a running version of the community service then you can replace steps 1 and 2 with the following command:
docker-compose run swagger generate -i http://[community-service-host:port]/explorer/swagger.json -l php -o /var/usr/client -c /var/usr/swagger/config.json
This is a checklist of steps for creating new widgets
docker-compose run web drush en field_ui
docker-compose run web drush cex -y
(You will need to cherry pick the config chances specific to the widget).eslintrc
in the root of the project is a duplicate of Drupal 8's .eslintrc
file. This is needed because Scrutinizer assumes that the ESLint config file is placed in the root.