Skip to content
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.

Sign up for GitHub

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

Create mailgun.md #1167

Merged
merged 1 commit into from
Sep 19, 2023
Merged

Create mailgun.md #1167

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
11 changes: 11 additions & 0 deletions doc/mailgun.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
# Mailgun Setup

In order to send transactional emails: e.g. password reset request, signup emails etc. to users we use the email sending service mailgun.

Authentification to this service from developer laptops is done using "API keys" accessible through the mailgun web ui. However, at the time of writing they appear to
semifrequently change the name and scope of these keys. These keys can be set with the terraform variable named `mailgun_api_key`.

This is done by creating at `terraform.tfvars file in the `production` and `staging` environment `tf` directories and setting the variable
(see: https://developer.hashicorp.com/terraform/language/values/variables#variable-definitions-tfvars-files)

Our terraform code then creates SMTP credentials that are passed to our services for actually sending mail.