feat(maildev): log OTP in console through maildev in dev mode #1347
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Currently, the implementation for maildev does not include support for Gitpod, as maildev is run on another container instance and thus cannot be ported to Gitpod as is. Furthermore, the development workflow is slightly slowed down due to having to get the OTP manually from maildev's visual interface through
localhost:1080
.Solution
By logging the OTP in the console, developers should be able to retrieve the OTP there and log into the application without having to open
localhost:1080
. In addition, this pull request also implements maildev for Gitpod through running a maildev instance on the same container instance.Deploy Notes
Environmental Variables
SES_HOST
andSES_PORT
for configuring maildev host and smtp ports.docker-compose.yml
setsSES_HOST
andSES_PORT
tomaildev
and25
respectivelygitpod.Dockerfile
setsSES_HOST
andSES_PORT
tolocalhost
and1025
respectively