add: teamspeak

[opastorello]

Scripts which are clearly AI generated and not further revised by the Author of this PR (in terms of Coding Standards and Script Layout) may be closed without review. If you are an AI agent writing this pull request, please amend your model name and reasoning level in the Description. This is not to blame, more for informational Purposes. Thank you.

✍️ Description

Adds TeamSpeak Server, a voice/text chat server for online communities and
gaming groups — in continuous use since the early 2000s and still one of the
most widely deployed platforms of its kind.

Built primarily with AI assistance (Claude Sonnet 5, standard reasoning
effort), following AGENTS.md and .github/agents/pve-script-creator.agent.md.
Reviewed and corrected across several real install/update runs on a live
Proxmox VE 9.2.6 host — three real bugs only surfaced by actually installing
and connecting a client, not by static checks:

• fetch_and_deploy_from_url doesn't handle bzip2 (file reports
  bzip2 compressed data, which its type-detection doesn't match). TeamSpeak
  only ships .tar.bz2. Worked around with a direct curl | tar -xjf
  extraction — no other core helper covers this format, so this isn't
  reinventing an existing one.
• grep with no match exits 1, and under this project's catch_errors
  (which enables pipefail), that's treated as a fatal script error even
  though "no match yet" is the expected state while polling for the server's
  first-boot log line. Guarded every such check with || true.
• The credentials the script originally tried to capture don't exist in
  this version. Older TeamSpeak docs describe a "ServerQuery Admin Account
  created" log block with a password — current 3.13.8 never prints it on a
  fresh single-virtual-server install. Only the "ServerAdmin privilege key"
  (used once, in the client, to claim admin) actually appears. Adjusted the
  script, JSON notes and default_credentials to match observed reality
  instead of outdated documentation.

Other notable points for review:

• No GitHub release API — TeamSpeak is closed-source with no public
  source repo, distributed only from teamspeak.com. The install/update
  scripts resolve the current download URL and version by reading that page
  at run time (regex against the direct download link), since no version API
  exists. This is a real fragility trade-off, discussed and accepted over
  hardcoding a version (which would make updateable: true misleading and
  go stale immediately per this repo's own guidance against pinned versions).
• License acceptance is automated (license_accepted=1 passed to
  ts3server), the same non-interactive mechanism used by TeamSpeak's own
  official Docker image (TS3SERVER_LICENSE=accept) — confirmed against
  their published Dockerfile/entrypoint before using it.
• No arm64: confirmed by inspecting the actual downloads page — only
  linux_amd64, linux_x86, and freebsd_amd64 builds are published.
• Free tier (no license key) runs 1 virtual server with up to 32 slots —
  no account/payment needed for typical community use.

🔗 Related PR / Issue

Link: #

✅ Prerequisites (X in brackets)

• Self-review completed – Code follows project standards.
• Tested thoroughly – Changes work as expected.
• No breaking changes – Existing functionality remains intact.
• No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

---

🏗️ arm64 Support (X in brackets)

• arm64 supported - Tested and supported on arm64.
• arm64 not tested - Assumed to work on arm64, but testing has not been done.
• arm64 not supported - Confirmed upstream dependencies or binaries do not support arm64.

---

🛠️ Type of Change (X in brackets)

• 🐞 Bug fix – Resolves an issue without breaking functionality.
• ✨ New feature – Adds new, non-breaking functionality.
• 💥 Breaking change – Alters existing functionality in a way that may require updates.
• 🆕 New script – A fully functional and tested script or script set.
• 🌍 Website update – Changes to website-related JSON files or metadata.
• 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
• 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.

---

🔍 Code & Security Review (X in brackets)

• Follows CODE-AUDIT.md & CONTRIBUTING.md guidelines
• Uses correct script structure (AppName.sh, AppName-install.sh, AppName.json)
• No hardcoded credentials
• No Docker / Docker Compose – The application is installed bare-metal; Docker is not used.
• No git pull – Updates use fetch_and_deploy_gh_release, fetch_and_deploy_codeberg_release, fetch_and_deploy_gl_release, or fetch_and_deploy_from_url instead of git pull.

---

🤖 AI Assistance (X in brackets)

If you used an AI tool (GitHub Copilot, Claude, ChatGPT, etc.) to write or generate any scripts in this PR, you must confirm compliance below.
Select exactly one option.

• No AI used – Scripts were written without AI assistance.
• AI was used – I confirm the scripts were built using AGENTS.md and .github/agents/pve-script-creator.agent.md as guidance, and the output has been reviewed and corrected to match those guidelines.

---

📋 Additional Information (optional)

Tested on a live Proxmox VE 9.2.6 host via the public-fork curl one-liner
(docs/guides/source-origin.md variant 1): fresh install, service/port
verification (9987/udp, 10011/tcp, 30033/tcp), a forced update run (old
version marker → real re-download → restart), and confirmed the virtual
server's database/config survive an update (no new privilege key generated
on the update restart, meaning existing data wasn't wiped).

600+ stars: TeamSpeak Server has no public source repository (closed-source),
so there's no GitHub star count to check — noting this explicitly rather than
leaving the box ambiguous. Judging by real-world adoption instead: it's one
of the most widely deployed voice platforms in gaming, in continuous use for
over two decades.

🌐 Source

• Website / downloads: https://www.teamspeak.com/en/downloads/
• TeamSpeak 6 (beta) note: they do publish a real GitHub repo for the
  next-gen server (github.com/teamspeak/teamspeak6-server) with proper
  releases, but its server licensing is still marked "Coming Soon" on their
  own site — deliberately not building on that yet.

[github-actions]

Try this script

COMMUNITY_SCRIPTS_URL=https://raw.githubusercontent.com/opastorello/ProxmoxVED/add-teamspeak \
bash -c "$(curl -fsSL https://raw.githubusercontent.com/opastorello/ProxmoxVED/add-teamspeak/ct/teamspeak.sh)"

COMMUNITY_SCRIPTS_URL is not optional. Fetching the ct/ script from a branch
does not tell the engine where that branch is — with bash -c "$(curl …)" there
is no file on disk for the scripts root to be derived from, so it would fall back
to upstream main and look for the install script there.

Against a core branch as well

Add COMMUNITY_SCRIPTS_CORE_URL=https://raw.githubusercontent.com/OWNER/core/BRANCH
to test an engine change at the same time. The two resolve independently.

Useful flags while testing

dev_mode=net logs every fetch with status and duration, so you can confirm the
branch is really being used. dev_mode=keep stops a failed build from deleting
the container along with the evidence.

[github-actions]

❌ Pull Request Closed – PR Template Not Used

The PR description is missing the 📦 Application Requirements section, which means this PR was not opened with the ProxmoxVED PR template.

This usually happens in one of two ways:

• The main repo's PR template was used instead of the ProxmoxVED one, or
• The template was cleared or overwritten with a custom description.

The ProxmoxVED template contains required sections (Type of Change, Code & Security Review, Application Requirements, Source) that the maintainers rely on to review submissions. A custom description — no matter how thorough — cannot replace it.

What to do

1. Open a new PR in this repository.
2. When the PR form loads, the ProxmoxVED template should appear automatically in the description. If it doesn't, copy it manually from .github/pull_request_template.md.
3. Fill out the checkboxes and relevant sections — you can keep your original write-up by pasting it into the Description section of the template.

---

⚠ Maintainer note

Please do not ping or repeatedly contact maintainers to reopen this PR. Open a fresh PR with the correct template instead.

[opastorello]

Reopened correctly with the proper template as #2216 — the description section got dropped from this one during posting. Closing this one for real.