Add Tip to using MailHog during developement #9688
Conversation
Add Tip to using MailHog during developement
email/dev_environment.rst
Outdated
| @@ -13,6 +13,11 @@ choices when it comes to handling email during development: (a) disabling the | |||
| sending of email altogether or (b) sending all email to a specific | |||
| address (with optional exceptions). | |||
|
|
|||
| .. tip:: | |||
|
|
|||
| for testing emails during application development, and to make tests simple | |||
There was a problem hiding this comment.
- for testing emails during application development, and to make tests simple
- to web designers, you can use `MailHog`_.
+ For testing emails during development you can use `MailHog`_.|
I've never used this tool before. Before merging this, we'd need to hear opinions about this tool from Symfony developers who have used it. Thanks! |
|
What's is the advantage over https://mailcatcher.me recommended by SwiftMailer docs? |
|
Surely this is just spam |
|
I'm all for recommending MailHog. I've used it for at least three years now, as it's easy to setup, has a good UI and just works. |
|
@kiler129 Mailhog is an alternative for Mailcatcher that doesnt require any special dependencies like Ruby, so installation is very fast! Just download the binary and run it. |
|
In all the projects I could see, when the mail was not disabled, it was mailcatcher that was used. |
|
@zairigimad are You sure that project is live? the latest commit was a year ago and there is a lot of issues there. I prefer to use mailtrap.io |
|
Mailcatcher is really easy to set up, especially in docker (just create a compose service based on mailcatcher & share networks and that's all), what are the benefits of MailHog? What's the difference? |
|
This is now merged. Thank you all for your comments! |
… javiereguiluz) This PR was submitted for the 4.0 branch but it was merged into the 2.8 branch instead (closes #9688). Discussion ---------- Add Tip to using MailHog during developement Add Tip to using MailHog during developement <!-- If your pull request fixes a BUG, use the oldest maintained branch that contains the bug (see https://symfony.com/roadmap for the list of maintained branches). If your pull request documents a NEW FEATURE, use the same Symfony branch where the feature was introduced (and `master` for features of unreleased versions). --> Commits ------- 85009fc Removed some whitespace 731986e Reworded the tip contents acb3abd Add Tip to using MailHog during developement
Add Tip to using MailHog during developement