Why are we using Composer? Because it's standartised way how to handle project dependencies in PHP world.
Why are we using Docker? Docker allows everyone to have the same environment, so it means no more "It's working for me."
@TODO: Gulp/Grunt
- checkout this repository
- go into directory where your repository is installed
- run
composer install
, which will download all dependencies - run your docker containers with
pigmy up
(Linux) oramazeeio-cachalot up
(Mac) and rundocker-compose up -d
to assure that your containers are running. - log into container using
docker-compose exec --user drupal drupal bash
- develop
- install project by going to your-project-url/core/install.php
- select 'Slovak' language in the first step.
- select 'Config installer' install profile in the second step.
- rest of the required values for the rest of install profile should be set up automatically.
- Autoloader is implemented to use the generated composer autoloader in
vendor/autoload.php
, instead of the one provided by Drupal (web/vendor/autoload.php
). - Modules (packages of type
drupal-module
) will be placed inweb/modules/contrib/
- Theme (packages of type
drupal-theme
) will be placed inweb/themes/contrib/
- Profiles (packages of type
drupal-profile
) will be placed inweb/profiles/contrib/
- Creates default writable versions of
settings.php
andservices.yml
. - Creates
sites/default/files
-directory. - Latest version of drush is installed locally for use at
vendor/bin/drush
. - Latest version of DrupalConsole is installed locally for use at
vendor/bin/drupal
.
If you need to apply patches (depending on the project being modified, a pull request is often a better solution), you can do so with the composer-patches plugin.
To add a patch to drupal module foobar insert the patches section in the extra section of composer.json:
"extra": {
"patches": {
"drupal/foobar": {
"Patch description": "URL to patch"
}
}
}
Follow the steps below to update your core files.
- Run
composer update drupal/core --with-dependencies
to update Drupal Core and its dependencies. - Run
git diff
to determine if any of the scaffolding files have changed. Review the files for any changes and restore any customizations to.htaccess
orrobots.txt
. - Commit everything all together in a single commit, so
web
will remain in sync with thecore
when checking out branches or runninggit bisect
. - In the event that there are non-trivial conflicts in step 2, you may wish
to perform these steps on a branch, and use
git merge
to combine the updated core files with your customized files. This facilitates the use of a three-way merge tool such as kdiff3. This setup is not necessary if your changes are simple; keeping all of your modifications at the beginning or end of the file is a good strategy to keep merges easy.