is the `mail_catcher` service behavior and usage d...
# docker
r
is the
mail_catcher
service behavior and usage documented somewhere?
r
I don't get how it works, on that page it has that custom_endpoints setting but in docker/generator/src/templates/env/common.env.twig it hard codes the host to mail_catcher
I can't even override those in deploy.yml
or disable the whole thing, how do I do that 😄
l
you can test via forgot password or subscribe for the newsletter
ah I misunderstood ... I thought you want to test it
r
well that would be a good start
as I see it the defaults cannot work
l
it does work for me with almost the default dev docker setup, tested with both scenarios above
subscribe to the newsletter with your email, it should popup in the mailhog inbox
so now I need to figure out how to disable mailhog
well or just give up since it works in the cloud env 😄
😄 1
so that doc is a bit misleading, you don't need that
also if I need to test actual sending locally I would just use my own ENV variables in config.php
l
I found this in the env files of the docker sdk
Copy code
SPRYKER_SMTP_HOST=mail_catcher
SPRYKER_SMTP_PORT=1025
I suppose you've either configure DSN for the corresponding provider available (https://symfony.com/doc/current/mailer.html) or create and register your custom provider
a
Mail catcher is needed for the local development. Can be enabled or disabled via deploy file - https://github.com/spryker-shop/suite/blob/master/deploy.dev.yml#L257-L260. If you need to disable it, just remove it from the deploy file. Don't forget to run
docker/sdk bootstrap {your_deploy_file}
each time you make changes there. In our PaaS mail catcher isn't available OOTB as there is AWS SES in place.
r
yeah I figured it out. Not the best documentation on that..