Dustin C. Hatch
208fadd2ba
I am going to use the *postgresql* group for the dedicated database servers. The configuration for those machines will be quite a bit different than for the one existing machine that is a member of that group already: the Nextcloud server. Rather than undefine/override all the group-level settings at the host level, I have removed the Nextcloud server from the *postgresql* group, and updated the `nextcloud.yml` playbook to apply the *postgresql-server* role itself. Eventually, I want to move the Nextcloud database to the central database servers. At that point, I will remove the *postgresql-server* role from the `nextcloud.yml` playbook.
25 lines
604 B
YAML
25 lines
604 B
YAML
nextcloud_server_name: nextcloud.pyrocufflink.net
|
|
apache_server_name: '{{ nextcloud_server_name }}'
|
|
pg_hba_extra:
|
|
- type: host
|
|
database: nextcloud
|
|
user: nextcloud
|
|
address: ::1/128
|
|
method: md5
|
|
nextcloud_trusted_proxies:
|
|
- 127.0.0.1
|
|
- ::1
|
|
- '{{ lookup("dig", groups["public-web"][0]) }}'
|
|
nextcloud_trusted_domains:
|
|
- nextcloud.pyrocufflink.net
|
|
- nextcloud.pyrocufflink.blue
|
|
- '{{ ansible_fqdn }}'
|
|
nextcloud_smtp:
|
|
from: nextcloud@pyrocufflink.net
|
|
host: mail.pyrocufflink.blue
|
|
port: 25
|
|
dnf_automatic_exclude: nextcloud
|
|
|
|
postgresql_config_dir: /var/lib/pgsql/data
|
|
postgresql_allow_remote: false
|