README.md


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53

TeamSpeak 3 Server
==================

Role that deploys a TeamSpeak 3 server.
Inspired by [dharmab/ansible-playbooks/roles/teamspeak](https://github.com/dharmab/ansible-playbooks/tree/master/roles/teamspeak).

By incrementing the TeamSpeak 3 version number, and assigning the appropriate SHA256 checksum string, this role can also perform upgrades of TeamSpeak 3 servers. Provided those have been previously installed by this role (starting from this version of the role). CAUTION: Such a procedure is not well tested yet.

Requirements
------------

Tested on Ubuntu 16.04.1.

Role Variables
--------------

defaults/main.yml:

* teamspeak.user: User to run the teamspeak server. Defaults to "teamspeak".
* teamspeak.comment: User comment field. Defaults to "Teamspeak 3 user".
* teamspeak.home: Home directory for the teamspeak user. Will also be used to install the teamspeak server in. Defaults to "/opt/teamspeak".
* teamspeak.shell: Shell for the teamspeak user. Defaults to "/usr/sbin/nologin".
* teamspeak.symlink: Name of symlink to point to current TeamSpeak 3 server directory. Defaults to "current".
* teamspeak.version: Version of Teamspeak 3 Server to install. Defaults to "3.0.12.4".
* teamspeak.checksum: SHA256 checksum of archive of TeamSpeak 3 server version for verification purposes. Example: "sha256:6bb0e8c8974fa5739b90e1806687128342b3ab36510944f576942e67df7a1bd9"

vars/{debian,redhat}.yml:

* systemd_service_file_path: Path where Systemd service files are installed.

Dependencies
------------

rsync should be installed on the host to perform TeamSpeak 3 Server upgrades, used by the "synchronize" module.

Example Playbook
----------------

Including an example of how to use your role (for instance, with variables passed in as parameters) is always nice for users too:

    - hosts: ts3servers
      roles:
         - teamspeak

License
-------

MIT

Author Information
------------------

Stefan Joosten <stefan@sjoosten.nl>