discourse issueshttps://git.coop/webarch/discourse/-/issues2023-04-20T08:47:16Zhttps://git.coop/webarch/discourse/-/issues/6Refactor all postfix tasks into a postfix role2023-04-20T08:47:16ZChris Croomechris@webarchitects.co.ukRefactor all postfix tasks into a postfix roleChris Croomechris@webarchitects.co.ukChris Croomechris@webarchitects.co.ukhttps://git.coop/webarch/discourse/-/issues/5Generate the whole of app.yml from a variable rather than template bits of it2023-04-20T08:46:21ZChris Croomechris@webarchitects.co.ukGenerate the whole of app.yml from a variable rather than template bits of itRather than templating sections of the `app.yml` file, based on the [standalone.yml template](https://github.com/discourse/discourse_docker/blob/main/samples/standalone.yml) it <strike>might</strike> *would* make sense to generate the wh...Rather than templating sections of the `app.yml` file, based on the [standalone.yml template](https://github.com/discourse/discourse_docker/blob/main/samples/standalone.yml) it <strike>might</strike> *would* make sense to generate the whole file as YAML, for example using a template like this:
```yml
---
# {{ ansible_managed }}
# See https://github.com/discourse/discourse_docker/blob/main/samples/standalone.yml for the default options
{{ discourse_app | to_nice_yaml(indent=4, width=1200) }}
...
```
Currently the [yq](https://git.coop/webarch/yq) role is needed to make the `app.yml` that is generated valid YAML.Chris Croomechris@webarchitects.co.ukChris Croomechris@webarchitects.co.ukhttps://git.coop/webarch/discourse/-/issues/3root and other email aliases2019-11-13T15:13:10ZChris Croomechris@webarchitects.co.ukroot and other email aliasesWe need some Postfix config (or the Ruby script amending?) to *not* send `root` and other email to Discourse, perhaps if there is an address in `/etc/aliases` then don't pass the email to Discourse but let Postfix deal with it?
This isn...We need some Postfix config (or the Ruby script amending?) to *not* send `root` and other email to Discourse, perhaps if there is an address in `/etc/aliases` then don't pass the email to Discourse but let Postfix deal with it?
This isn't super-urgent @kate but it would be nice to have it working properly... An example:
```
Nov 13 15:05:14 discourse receive-mail[4944]: Recipient: root@discourse.webarchitects.org.uk
Nov 13 15:05:14 discourse postfix/pipe[4882]: DDC6D4165D: to=<root@discourse.webarchitects.org.uk>, orig_to=<root>, relay=discourse, delay=0.34, delays=0.11/0/0/0.23, dsn=2.0.0, status=sent (delivered via discourse service)
Nov 13 15:05:14 discourse postfix/qmgr[761]: DDC6D4165D: removed
```Kate DawsonKate Dawsonhttps://git.coop/webarch/discourse/-/issues/1Set vm.overcommit_memory2019-03-13T23:05:22ZChris Croomechris@webarchitects.co.ukSet vm.overcommit_memory```
185:M 13 Mar 2019 23:03:36.212 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
185:M 13 Mar 2019 23:03:36.213 # Server initialized
185:M 13 Mar 2019 ...```
185:M 13 Mar 2019 23:03:36.212 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
185:M 13 Mar 2019 23:03:36.213 # Server initialized
185:M 13 Mar 2019 23:03:36.213 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
185:M 13 Mar 2019 23:03:36.228 * DB loaded from disk: 0.014 seconds
```Chris Croomechris@webarchitects.co.ukChris Croomechris@webarchitects.co.uk