projects / discourse_docker.git / blame
| Commit | Line | Data |
|---|---|---|
| 5a92b90f MP |
1 | ## this is the incoming mail receiver container template |
| 2 | ## | |
| 3 | ## After making changes to this file, you MUST rebuild | |
| 4 | ## /var/discourse/launcher rebuild mail-receiver | |
| 5 | ## | |
| 6 | ## BE *VERY* CAREFUL WHEN EDITING! | |
| 7 | ## YAML FILES ARE SUPER SUPER SENSITIVE TO MISTAKES IN WHITESPACE OR ALIGNMENT! | |
| 8 | ## visit http://www.yamllint.com/ to validate this file as needed | |
| 9 | ||
| 10 | base_image: discourse/mail-receiver:1.0.0 | |
| 93e6a609 | 11 | update_pups: false |
| 5a92b90f MP |
12 | |
| 13 | expose: | |
| 14 | - "25:25" # SMTP | |
| 15 | ||
| 16 | env: | |
| 17 | LANG: en_US.UTF-8 | |
| 18 | ||
| a502da0e MP |
19 | ## Where e-mail to your forum should be sent. In general, it's perfectly fine |
| 20 | ## to use the same domain as the forum itself here. | |
| 21 | MAIL_DOMAIN: discourse.example.com | |
| 22 | ||
| 5a92b90f MP |
23 | ## The URL of the mail processing endpoint of your Discourse forum. |
| 24 | ## This is simply your forum's base URL, with `/admin/email/handle_mail` | |
| 25 | ## appended. Be careful if you're running a subfolder setup -- in that case, | |
| 26 | ## the URL needs to have the subfolder included! | |
| 27 | DISCOURSE_MAIL_ENDPOINT: 'http://discourse.example.com/admin/email/handle_mail' | |
| 28 | ||
| 29 | ## The master API key of your Discourse forum. You can get this from | |
| 30 | ## the "API" tab of your admin panel. | |
| 18d87dd3 | 31 | DISCOURSE_API_KEY: abcdefghijklmnop |
| 5a92b90f MP |
32 | |
| 33 | ## The username to use for processing incoming e-mail. Unless you have | |
| 34 | ## renamed the `system` user, you should leave this as-is. | |
| 35 | DISCOURSE_API_USERNAME: system | |
| 36 | ||
| 37 | volumes: | |
| 38 | - volume: | |
| 39 | host: /var/discourse/shared/mail-receiver/postfix-spool | |
| 40 | guest: /var/spool/postfix |