Mail production

[ArmandArthur]

Hello the team,

I don't see in the documentation how to send emails in production.

Have you somes advices please?

[zpi12lmm]

I think you should read this documentation.
The main point for the prod environment is the choice of transport through which emails will be delivered.
For dev environments, emails are not sent directly to recipients, these emails will be intercepted by a special service, with which you can debug them correctly.
The implementation of sending emails for dev and prod environments is the same.

[ArmandArthur]

Thank you, i know it.
Emails are intercepted in production, can i remove mailpit in prod? how please

[ArmandArthur]

Up please?

[zpi12lmm]

Interception only works for development mode, so you don't need to disable anything for production mode.

[ArmandArthur]

In production, i have mailtip which is enable.
in compose-override.yaml, maybe remove the mailtip configuration?

[zpi12lmm]

For production mode, you will need to run your docker compose with the following files: compose.yaml, compose.prod.yaml

[ArmandArthur]

I did it? Are you sure?

[zpi12lmm]

сheck this documentation: https://github.com/dunglas/symfony-docker/blob/main/docs/production.md

there you will find a line of the following pattern docker compose -f compose.yaml -f compose.prod.yaml build --pull --no-cache, this is what you need to do

[ArmandArthur]

I do this of course last time.

[ArmandArthur]

Maybe if i have not installed mailer php from composer, it's use mailtip?

[zpi12lmm]

everything I wrote was related to the fact that you are already using the mailer component
If you didn't install it, I don't know how you have custom email setup

[ArmandArthur]

I could try it when my developement is advanced. thank you

[zpi12lmm]

What kind of mailtip is this? Is there a third-party service? Is there a link to it?

[ArmandArthur]

I don't know, it's myDomain.com:8025

[zpi12lmm]

I think you have this interceptor: https://github.com/axllent/mailpit
It is automatically added to file compose.override.yaml when you install the mailer component.
If this is the case, then it will be enough for you to follow the steps I gave you above.

[ArmandArthur]

it's possible, i come back here when i rebuild the container.

[zpi12lmm]

it's easy to check, file composer.json should have dependency symfony/mailer, if it does, then this is it

[ArmandArthur]

I watch my configuration in production.
My composer.json have symfony/mailer and the command used was SERVER_NAME="*" APP_SECRET= CADDY_MERCURE_JWT_SECRET=***** docker compose -f compose.yaml -f compose.prod.yaml up --wait

[zpi12lmm]

Well, all you have to do is choose the necessary transport, install it, add access keys, and that's it, this particular transport will be used in production.