Skip to main content



Before doing any migration back up your database in case the whole process goes south.

Version 10

Website name

We introduced a new environment variable, WEBSITE_NAME. It identifies your instance uniquely; for now, it will be used by the new uploader, but more use-cases are surely coming.

We also added support for expansion of environment variables, so now you can re-use your WEBSITE_NAME, for example:



The new version requires a Redis database; it is used to cache some data and store game logs. Follow site components deployment documentation to learn how to set it up.


Version 10 comes with an integrated uploader that captures in-game logs and uploads them when a match ends. It also lets you access game server logs directly via the webpage.

For the integration to work, you need to grab your API key here and put it in your .env file:


Uploading logs via the backend means that you need to disable log upload on your gameservers; otherwise all the logs are going to be doubled. To disable uploading logs to on your gameservers empty the LOGS_TF_APIKEY env variable:

# gameserver.env


In older versions of the project there was a typo in the environment file that we have fixed in version 9. However, the typo was still allowed alongside the correct variable name. We got rid of the typo in version 10, so make sure you take care of it in your .env file.

# Old variable name, wrong

# New variable name, typo fixed

Review privacy policy

To be compliant with the GDPR we added a new document - privacy policy. It is stored on the server and can be edited via your admin panel. It is short and contains only necessary information, so please take a look at it and update the link to your website, as it defaults to