2.1. gnuhealth

The playbook gnuhealth.yml installs the GNU Health Hospital Information System (HIS) which is the core of GNU Health.

Note that the role gnuhealth is described in the roles chapter and this part only targets how the playbook combines different roles.

The following booleans in ìnventories/dev/group_vars/gnuhealth control whether substeps are executed are not (listed in execution order):

  1. locale (default: false)

  2. certificate_authority (default: true)

  3. postgresql (default: true)

  4. application (default: true, implies gnuhealth & uwsgi role)

  5. nginx (default: true)

  6. backup (default: false, implies barman & restic role)

  7. zabbix (default: false)

  8. fail2ban (default: false)

  9. unattended_upgrades (default: false)

  10. postfix (default: false)

  11. ssmtp (default: false)

  12. logwatch (default: false, needs postfix exclusive-or ssmtp)

  13. systemd_alert (default: false)

  14. timezone (default: false)

  15. nftables (default: false)

Substeps are vastly named after the corresponding roles.

If you call the _minimal playbook the booleans are ignored anyway and only the roles for the sub steps which are true by default get included. Configuration steps for SSH or TLS for distributed systems are also skipped.

The minimal playbook contains the following roles: check, certificate, postgresql, gnuhealth, uwsgi, nginx and gnuhealth-client. The latter usually belongs to the desktop playbook but the minimal scenario is expected to be everything in one system anyway thus it also calls the role for the client to connect to the server.

Check the chapter Roles for details about all the integrated roles.