resolve the sendmail error/warning upon initialization.

[martinfrances107]

I have listed below the output in response to initializing drupal.

In another PR I mistakenly reported the "Unable to send email." error was new

Tonight I looked back at the contentacms/contenta_docker:master repo and I see the error is an existing issue.

When I say error ... it does NOT prevent to initialization from operating correctly.

docker exec -it contentadocker_php_1 init-drupal Generating RSA private key, 2048 bit long modulus .......................+++ ..................+++ e is 65537 (0x10001) writing RSA key You are about to DROP all tables in your 'contenta' database. Do you want to continue? (y/n): y Starting Drupal installation. This takes a while. Consider using the [ok] --notify global option. sh: /usr/sbin/sendmail: No such file or directory Installation complete. [ok] Unable to send email. Contact the site administrator if the problem [error] persists. Recipe magazin installed [status] Congratulations, you installed Contenta JSON API!

[pcambra]

Would including mailhog in docker compose solve this issue?

[martinfrances107]

Would including mailhog in docker compose solve this issue?

I was thinking about that ....

I don't have mailhog on my local development setup... but there are plenty of drupal8 docker solutions that have a mailhog definition in their docker-composer.yml files - so by copying we can have a good starting point.

When running this project as it stands I can get admin access via a one-time URL and proceed from there.

To speak on the other side of the argument...

The performance of this project, for me is slow....there are a few improvements we could make .... adding a new container will slow the project further.... so if we could get away with mailhog then - I could list that as a advantage.

On the contenta roadmap ... would adding mailhog solve other problems?.... I do not have a wide enough of a pserective to have a valid opinion.