What are the benifets of utilizing a database for a self hosted TS6 server?

Does the TS6 docker come with a database or do you have to set it up in the contain yourself, and what are the pros of setting up a database for your server? I’m using Casaos to manage my docker images. I used this docker compose to setup my TS6 server:

services:
teamspeak:
image: teamspeaksystems/teamspeak6-server:latest
container_name: teamspeak-server
restart: unless-stopped
ports:

  • “9987:9987/udp” # Voice Port

  • “30033:30033/tcp” # File Transfer

  • “10080:10080/tcp” # Web Query

environment:

  • TSSERVER_LICENSE_ACCEPTED=accept
    volumes:
  • teamspeak-data:/var/tsserve

volumes:
teamspeak-data:
name: teamspeak-data

The TS6 server support both SQLite and MariaDB, but from what I’ve heard, SQLite will be enough for most use cases.

You can find example compose files for both setups on the repository:

I’m not super familiar with databases. What are the biggest benefits of using a database vs not using one?

In both cases you are using a database, just that SQLite is a file one, and MariaDB is a network one. MariaDB would be a better fit in case of multiple servers trying to access a single database at once. But it comes with additional resource usage and requires maintenance. For a simple use case like self-hosting a TS server, SQLite will be enough.

2 Likes

So what you’re saying is the basic docker compose I listed uses a database already?
Sorry for the dumb questions! I’m not very smart about this stuff. X3

Yep, it uses SQLite by default.