Skip to content

Ansible role to deploy ZNC server on CentOS/RHEL 7.x system

License

Notifications You must be signed in to change notification settings

jwflory/ansible-role-znc

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

21 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Ansible Role: ZNC

Ansible role to deploy ZNC server on CentOS/RHEL 7.x system

Requirements

No special requirements. Note this role requires root access; either run it in a playbook with a global become: yes or invoke the role in your playbook:

- hosts: servers
  roles:
    - role: jwflory.teleirc
      become: yes

Role Variables

For vault_znc_conf.admin_user.password settings, use znc --makepass to generate the password hashes and salts. You must update suggested Ansible Vault variables to your hash and salt for a successful initial login.

znc_fqdn: example.com
znc_conf:
  admin_user:
    znc_username: znc-admin
    nick: znc-admin
    alt_nick: znc-admin_
    ident: zncadmin
    real_name: "Default ZNC admin user"
    password:
      hash: "{{ vault_znc_conf.admin_user.password.hash }}"
      salt: "{{ vault_znc_conf.admin_user.password.salt }}"
    primary_network:
      network_name: freenode
      server: "chat.freenode.net +6697"
  listener:
    port: 6697
    ipv4: true
    ipv6: true
    ssl: true
  version: 1.7.2
  • : to be written
  • : to be written
  • : to be written

Dependencies

None.

Example Playbook

- hosts: znc-host
  roles:
     - role: jwflory.znc

License

Mozilla Public License 2.0

Author(s) accept changes made to vars/ to be omitted in published derivative work, as these are understood to be deployment-specific. Modifications to other aspects of the Ansible Role that others could benefit from are expected to be open.

Author Information

This role was created in 2019 by Justin W. Flory. Find him on GitHub and LinkedIn.