Initial configuration is done once per project (e.g. by a team lead) and committed into the project repo.
docker-compose.yml
file and an optional .drude
folder are good indicators that a project is using DDE.
On Windows make sure your projects
folder is not inside %USERPROFILE%/.babun
folder.
-
Edit
settings.php
for your site (see Drupal settings). -
Open console (Babun on Windows) and cd into
<projects/your-drupal-site>
. -
Install default DDE configuration file (downloads the latest
docker-compose.yml
):dsh install drude-config
-
Update
docker-compose.yml
as necessary. -
Start DDE with:
dsh up
This is optional, but highly recommended.
Site provisioning can be automated via a custom command.
E.g. dsh init
will call .drude/commands/init
, where you can put project specific initialization tasks like:
- initialize DDE configuration
- import database or perform a site install
- compile sass
- run update, revert features, clear caches, etc.
- enable/disable modules, update variable values
- run Behat tests
For a fully working example of a DDE powered project (including dsh init
) take a look at: