drupal-project | Drupal projects designed to work | Continous Integration library

The command you tried to run will download the latest dev version of the project. If you want to modify versions, or anything that comes along with the project, you can do so by adding the --no-install flag to your command:

I think the confusion here comes from the word 'libraries'.

Composer is a tool for dependency management written in PHP.

PHP itself relies on a scripting engine (originally Zend, but there are alternatives like Facebook's HHVM, etc.), it works as a compiler and runtime engine and it needs 'libraries' - think of it as modules or extensions. These modules are mostly written in C, some in C++.

Having 'missing libraries' errors when Apache starts up does not mean Composer has missed any Drupal dependencies, it means PHP needs to be configured or rebuilt properly with the missing modules.

There are 3 types of modules (PHP's extensions membership):

• Core modules that cannot be left out of a PHP binary with compilation options.
• Core extension modules that are bundled with PHP core but not necessarily enabled.
• External modules that are not bundled with PHP core. These modules are available from a repository called PECL (PHP Extension Community Library).

For example, if you were to speedup Drupal or any PHP applications by caching both PHP code and user variables, you would need some opcode like APC. That said, adding APC settings to php.ini would not work as is without the corresponding module being compiled with PHP.

--stability dev switch does not have any effect in this case, so I would guess this is some leftover from old days (or the result of a lack of understanding how stability flags works in composer). In composer.json of this project there is already defined this setting:

Your drupal container doesn't know anything about mariadb container during the build. Only after you run docker-compose up the drupal and mariadb containers will be available for each other on the same network.

What you need to do is to run your drush after you start your containers with docker-compose up. You can use bash to accomplish that. For example, create start.bash file and put:

If your theme is part of your installation profile, it should be present in the composer.json file. Your developer should only use that theme as a base theme and create a sub-theme. Within that sub-theme, the developer can overwrite CSS as well as template files and template functions.

This is not composer-related. You're just missing a php-extension. I don't know what php-version you have or what Operation System is on your server. I post some examples for bash:

EDIT: NOW I HAVE FOUND YOUR VERSION:

CentOS-Example: