Here are the configuration options, set to the default values, for this service. If you are unsure about where this goes or what this means we highly recommend scanning the services documentation to get a good handle on how the magicks work.
services: myservice: type: mailhog:v1.0.0 portforward: false hogfrom: 
portforward will allow you to access this service externally by assigning a port directly on your host's
localhost. Note that
portforward can be set to either
true or a specific
port but we highly recommend you set it to
true unless you have pretty good knowledge of how port assignment works or you have a very compelling reason for needing a locked down port.
portforward: true will prevent inevitable port collisions and provide greater reliability and stability across Lando apps. That said, one downside of
portforward: true is that Docker will assign a different port every time you restart your application. You can read more about accessing services externally over here.
services: myservice: type: mailhog portforward: true
services: myservice: type: mailhog portforward: 1025
You will need to list the services the wish to hog mail from using the
hogfrom config key. Note that the services in the list should be other services in your application. They can be discovered by running lando info.
Config may differ!
While we will automatically configure the underlying
php service you choose to
hogfrom, you may need to consult the documentation for the specific type of service you are choosing to hogfrom.
An example of a Landofile's
services config that hogfroms a
php service called
appserver is shown below:
services: myservice: type: mailhog:v1.0.0 portforward: false hogfrom: - appserver appserver: type: php
Note that we will install the mhsendmail binary at
/usr/local/bin/mhsendmail in each
hogfrom service for you to use. Each of these services should also be able to access the MailHog STMP server using the
MH_SENDMAIL_SMTP_ADDR environment variable which is set to
sendmailhog:1025 by default.