Skip to content

Add Tip to using MailHog during developement #9688

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 3 commits into from
Closed
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions email/dev_environment.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

- 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`_.

to web designers, you can use `MailHog`_.

Disabling Sending
-----------------

Expand Down Expand Up @@ -241,3 +246,5 @@ the report with details of the sent emails.
by the submit URL used on the previous request (e.g. ``/contact/handle``).
The profiler's search feature allows you to load the profiler information
for any past requests.

.. _`MailHog`: https://github.com/mailhog/MailHog