You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+8-1Lines changed: 8 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,14 @@ There are two GitHub Actions workflows that run automatically when targeting cha
28
28
29
29
The [update](./update) directory contains a node program which will read the aliases mapping file, fetch the list of mail routes from Mailgun and update the routes to make sure they match the required state. The program is run by passing it a domain name as an argument (`update/update.js iojs.org`).
30
30
31
-
The Mailgun API key for the given domain is required. It can be found in the `admin_logins.md` file in the secrets repo (build/infra/), or directly via the Rackspace API. The key should be used as environment variable `MAILGUN_API_KEY` when running the program.
31
+
The Mailgun API key for the given domain is required. It can be found in the `admin_logins.md` file in the secrets repo (build/infra/), or directly via the Rackspace API. The key should be used as environment variable `MAILGUN_API_KEY` when running the program.
32
+
33
+
34
+
Optionally, you can create a `.env` file in the `update` directory with the following content:
35
+
36
+
```
37
+
MAILGUN_API_KEY=your-api-key
38
+
```
32
39
33
40
The programs can be used with `--dry-run` to verify the current status and what will be changed by an update.
0 commit comments