Note that Solr, Node and Varnish are not enabled by default. See the [customization](/composer/plugin/d4d#customization) chapter below to learn how you can enable them.
Note that Solr, Node and Varnish are not enabled by default. See the [customization](/composer/plugin/d4d#customization) chapter below to learn how you can enable them.
- Docker4Drupal creates a number of containers depending on the services you
- Docker4Drupal creates a number of containers depending on the services you
require, e.g.
require, e.g.
-`project1_apache_1`
-`project1_apache_1`
-`project1_mailhog_1`
-`project1_mailpit_1`
-`project1_mariadb_1`
-`project1_mariadb_1`
-`project1_php_1`
-`project1_php_1`
-`project1_pma_1`
-`project1_pma_1`
...
@@ -119,7 +119,7 @@ the following domain names will be used for the respective services:
...
@@ -119,7 +119,7 @@ the following domain names will be used for the respective services:
-`project1.docker.localhost:8000`: The Drupal website.
-`project1.docker.localhost:8000`: The Drupal website.
-`pma-project1.docker.localhost:8000`: PhpMyAdmin of the project.
-`pma-project1.docker.localhost:8000`: PhpMyAdmin of the project.
-`mailhog-project1.docker.localhost:8000`: The Mailhog service for the project.
-`mailpit-project1.docker.localhost:8000`: The Mailhog service for the project.
-`bs-project1.docker.localhost:8000`: Browsersync instance when running Gulp.
-`bs-project1.docker.localhost:8000`: Browsersync instance when running Gulp.
In other words, the project ID plus some service identifier are used as the
In other words, the project ID plus some service identifier are used as the
...
@@ -247,9 +247,31 @@ With this setup, you can debug both web requests coming from the browser and
...
@@ -247,9 +247,31 @@ With this setup, you can debug both web requests coming from the browser and
CLI commands for PHP which is executed inside the PHP container like e.g.
CLI commands for PHP which is executed inside the PHP container like e.g.
drush - all with the same setup.
drush - all with the same setup.
## Using MailPit
When using the [Docker4Drupal](../../composer/plugin/d4d/index.md), a MailPit service will be configured automatically by default.
This captures all outgoing email so that you can view those emails in a dashboard from your browser. Should you want
to release an email to see how it looks in you email client, MailPit provides a button to do that. This requires SMTP
server configuration, that you can provide in your local `.env` files like this:
```bash
MAILPIT_HOST=smtp.freesmtpservers.com
MAILPIT_PORT=25
MAILPIT_USERNAME=
MAILPIT_PASSWORD=
MAILPIT_STARTTLS=
MAILPIT_ALLOW_INSECURE=
MAILPIT_AUTH=none
MAILPIT_SECRET=
MAILPIT_RETURNPATH=
MAILPIT_RECIPIENT_ALLOW_LIST=
```
For more details about those parameters, please refer to [SMTP relay configuration](https://mailpit.axllent.org/docs/configuration/smtp-relay/#smtp-relay-configuration).
## Using MailHog
## Using MailHog
When using the [Docker4Drupal](../../composer/plugin/d4d/index.md), a MailHog service will be configured automatically.
When using the [Docker4Drupal](../../composer/plugin/d4d/index.md), a MailHog service can be configured.
This captures all outgoing email so that you can view those emails in a dashboard from your browser. Should you want
This captures all outgoing email so that you can view those emails in a dashboard from your browser. Should you want
to release an email to see how it looks in you email client, MailHog provides a button to do that. This requires SMTP
to release an email to see how it looks in you email client, MailHog provides a button to do that. This requires SMTP
server configuration, that you can provide in your local `.env` files like this:
server configuration, that you can provide in your local `.env` files like this: