This repository has everything you need to deploy four p1xbraten servers each on one or more Alpine Linux VPS, plus make commands to generate the corresponding /tourney cubescript.
You need a Alpine Linux box with a public IPv4 for this. Hetzner's CX22 or CAX11 "Cloud Servers" work nicely, with the latter scoring higher in benchmarks for the same price. Pick the Nuremberg data center (most players are located in the EU).
In order to register with the master server, outgoing traffic needs to originate from the ingress IP. Also, you need to be able to listen on two UDP ports per instance. Most "serverless" container hosting services will not work for those reasons. Fly.io at least supports UDP on arbitrary ports, but you won't be able to register with the master server since outgoing TCP traffic uses IPs you can't listen on. Plain old virtual Linux boxes usually don't have all these problems, and are billed by the hour these days, so just use those.
To get Alpine installed on the Hetzner VPS, follow this guide. After that, follow the Alpine docs. Make sure you can SSH into the server as root.
At this point, you might want to take a snapshot of your server in the Hetzner dashboard, to skip the Alpine setup in the future.
If you need another server in a different region, repeat these steps (or just create more servers from a snapshot). Note down the IPs of these servers, as you will need them to generate the player scripts.
To hide the tourney servers' IPs, you will need another VPS with another IPv4. The Makefile assumes it is provisioned the same way as the game servers.
Pre-flight checklist:
- Update the config at the top of the Makefile. You need the server IP(s) in the SERVER_ALLOCATION variable!
- Review server/root/server.cfg, especially
updatemaster(make sure it's 0 when using a proxy) - Make sure server/root/users.cfg contains the desired auth domain and a key for each tournament admin, with 'a' (admin) permissions
To deploy the servers, run make servers. This will generate tarballs of scripts and configuration, copy them to the server, then set up eight p1xbraten services. Wait for everything to finish, then verify that p1xbraten is listening on ports {1..8}000 (and some more).
If you want to use proxies, run make proxies now. This will (similar to the game servers) generate tarballs of scripts and configuration, copy them to the server, then set up eight sauer-proxy services. Wait for everything to finish, then verify that sauer-duels is listening on ports {1..8}000 (and more).
To generate the cubescript snippets, run make scripts. A participants.cfg and admins.cfg are generated and will show up next to this README. Share admins.cfg with all tournament admins. Share participants.cfg with all other participants. Participants should be able to simply copy and paste each line from participants.cfg fully into their console.
There is no secret knowledge in admins.cfg, but without admin privileges, you cannot use the additional commands.
Prints the tournament's map pool to the console.
Opens a GUI with buttons to connect to the tourney servers.
Prints the map pool to the console of everyone on the server.
Announces an upcoming match to everyone on the server. For example: /tourney_announce_match w00p RB EU2.
Moves all players to spectator. If you pass a team name, only players in that team are moved to spec.
After the tournament is over, fetch all the demos and logs: make artifacts. Then, simply delete the server(s) in Hetzner's dashboard. If you don't do this, you will be reminded when they bill you...