Upgrading to 3.0

Version 3.0 is the first release under the name Auto Tournament. Your players, teams, tournaments, matches, ratings, stats, servers, sign-ins and settings all move over. This page shows what changes, how to update a Docker install, and how to go back.

If you run 2.4.x for Counter-Strike 2, the short version is: back up, pull, restart, then move your servers to CS2 Server Manager. Your CS2 tournaments run the same way afterwards.

What changes

• The name. MatchZy Auto Tournament (MAT) is now Auto Tournament. Menus and pages were rebuilt, so the app looks different. The tasks are the same ones.
• CS2 is a module, not the whole app. Counter-Strike 2 now sits in a module next to a second one, manual reporting, which runs tournaments for games the platform cannot watch. A CS2 tournament still does everything it did: servers, veto, live scores, demos and stats.
• The licence changed. 3.0 and everything after it are under the PolyForm Noncommercial License 1.0.0. What that means for you is below.
• Ready Up on CS2 servers. Auto Tournament 3.x does not support MatchZy Enhanced. Servers run Ready Up, the native CS2 plugin. See Your CS2 servers.
• There is a new image name. sivertio/auto-tournament on Docker Hub, and ghcr.io/auto-tournament/auto-tournament on GitHub's registry.
• The docs moved from docs.sivert.io/docs/mat to docs.autotournament.gg. Old links redirect to the matching new page.

What does not change

Your docker-compose.yml and .env keep working as they are:

• The Compose service is still matchzy-tournament, and the containers are still matchzy-tournament-api and matchzy-postgres.
• The database is renamed from matchzy_tournament to auto_tournament on the first start, on the same volume. Your data stays, and you don't have to change DB_NAME: an .env or compose file that still says matchzy_tournament is read as the new name.
• Every environment variable in your .env keeps its name and its meaning, and 3.0 adds no required ones. The new things you can turn on, such as game search, are configured in the app's own settings.
• The app still listens on port 3069.

You do not have to change the image name

Every release is built once and published under all three names, so sivertio/matchzy-auto-tournament:latest gets 3.0 too. An install you never touch will update itself the next time you pull. Changing the name is tidier, and it is the name that will be documented from now on, but nothing breaks if you leave it.

The licence change

Up to and including 2.4.15, Auto Tournament was MIT-licensed. From 3.0 it is under the PolyForm Noncommercial License 1.0.0. The source is still public, and you can still read it, change it and share your changes.

If nobody earns money from your events, nothing changes for you. Personal and hobby use stays free, and so do tournaments and LAN parties where all entry fees and sponsor money go back into the event and nobody is paid or takes profit. Charities, schools and universities, public research, public safety or health and environmental protection organizations, and government bodies are free too, as the license lists them.

You need a licence if you earn money from it. That covers hosting Auto Tournament for other people for money, events where the organizer makes a profit, use inside a business, and being paid to set up or run servers or tournaments. The full list, and how to ask, is on Licensing and commercial use.

2.4.15 and earlier stay MIT. That does not change retroactively, and the old images stay on Docker Hub.

Fixes you get on the way

Three fixes in 3.0 change how an existing install behaves. Two of them need something from you.

Demos and event logs were being thrown away

In 2.4.x the app worked out the wrong folder for demos and event logs when running from the release image: it wrote them to /data inside the container instead of /app/data, which is the folder your ./data volume is mounted on. Everything written there lived in the container's own writable layer, so every update deleted every demo and event log.

3.0 writes to the right folder, and on the first start it moves anything still lying in the old one across. But a container that is replaced loses its writable layer, so if you want the demos and logs your current container is holding, copy them out before you update. Afterwards they are on your volume and survive updates.

Uploaded map images never appeared

Uploaded map images were written one folder above the one /map-images is served from, so the image was accepted and then never showed up. Worse, both folders were inside the container rather than on a volume, so whatever was there went away with the container anyway.

3.0 stores them under ./data/map-images, on the volume you already mount, and serves /map-images from there. Uploads show up, and they survive updates. Images your current container is still holding are in the container, so copy them out before you update — the map records already point at them, so they start rendering once they land on the volume.

Match configs are no longer public

GET /api/matches/:slug.json is the match config your CS2 servers download, and it used to answer anyone who asked. Match slugs are easy to guess (r1m1, r2m1, …), so anyone who could reach your API could read both rosters, Steam IDs, team names, the map list and the match setup.

In 3.0 the endpoint needs either the X-MatchZy-Token header with your SERVER_TOKEN, or an admin sign-in. Your servers need no change: the app now puts the header on the load command it sends them, and every version of the plugin understands it. Only two things are affected:

• Loading a config URL by hand in a server console now needs matchzy_loadmatch_url "<url>" "X-MatchZy-Token" "<SERVER_TOKEN>".
• Scripts or tools of your own that fetched a config anonymously now need the header or an admin token.

Before you start

• Your install runs 2.4.x with Docker Compose, as in Install. The upgrade is tested from 2.4.15; if you are on an older 2.4.x, update to 2.4.15 first.
• No match is running. The app restarts.
• You have the folder with your docker-compose.yml and .env. Run every command below in that folder.
• Your CS2 servers move to CS2 Server Manager and Ready Up. 3.x does not talk to MatchZy Enhanced; see Your CS2 servers.

Update

curl -fsS http://localhost:3069/api/settings/version

mkdir -p backups
docker compose exec -T postgres sh -c 'pg_dump -U "$POSTGRES_USER" "$POSTGRES_DB"' > "backups/autotournament-$(date +%F-%H%M%S).sql"

mkdir -p data
docker compose cp matchzy-tournament:/data/. ./data/

mkdir -p data/map-images
docker compose cp matchzy-tournament:/public/map-images/. ./data/map-images/

services:
  matchzy-tournament:
    image: sivertio/auto-tournament:3.0.0

sed -i.bak 's#sivertio/matchzy-auto-tournament:[^ ]*#sivertio/auto-tournament:3.0.0#' docker-compose.yml

docker compose pull
docker compose up -d

docker compose logs -f matchzy-tournament

curl -fsS http://localhost:3069/api/settings/version
curl -fsS http://localhost:3069/health

Go back to 2.4.15

3.0 only adds to the database — no table or column is dropped, renamed or rewritten — so 2.4.15 starts again on a database 3.0 has migrated, shows the same data, and can still be written to. That was tested by upgrading a 2.4.15 install to 3.0 and then booting 2.4.15 back onto the same database.

Anything created only in 3.0, such as a match report or a team captain, is invisible to 2.4.15. It stays in the database, and comes back if you move to 3.0 again.

services:
  matchzy-tournament:
    image: sivertio/matchzy-auto-tournament:2.4.15

grep -q '^DB_NAME=' .env && sed -i.bak 's/^DB_NAME=.*/DB_NAME=auto_tournament/' .env || echo 'DB_NAME=auto_tournament' >> .env

docker compose pull
docker compose up -d

curl -fsS http://localhost:3069/api/settings/version

docker compose stop matchzy-tournament
docker compose exec -T postgres sh -c 'dropdb -U "$POSTGRES_USER" "$POSTGRES_DB" && createdb -U "$POSTGRES_USER" "$POSTGRES_DB"'
docker compose exec -T postgres sh -c 'psql -U "$POSTGRES_USER" "$POSTGRES_DB"' < backups/autotournament-YYYY-MM-DD-HHMMSS.sql
docker compose up -d

If something goes wrong

• The app will not start. docker compose logs matchzy-tournament usually names the cause. A missing value in .env and a database it cannot reach are the two common ones.
• It won't start, and the log talks about the database name. The 2.x container is still running and connected to the old database (stop it first), or the database user may not rename it. The log line says which, with the exact command to run in the second case.
• Your data looks empty. Almost always a volume that was recreated, or a database called auto_tournament that already existed next to the old one (the log says both exist). Check that docker-compose.yml still points at the same volume as before.
• Anything else. Troubleshooting, or ask on Discord.