Technical Documentation

Upgrading Lootlocker

Last Updated: October 16, 20241.1 min read

Overview

Sometimes, you would want to update your backend repositories with the last changes pushed by Lootlocker available on gitlab.

Please note that it will not be an easy task since you will have to fix a lot of git conflicts and sometimes refactor your own work according to their changes since they often make those types of huge refactoring. Also note that the most sensible parts of the project are currently related to assets, files and players since that’s where most changes are made. If they make drastic changes like deprecating some stuff we actively use, you wouls want to discard their changes and keep ours.

To upgrade any of your repositories (it works the same with ll-backend, go-backend etc), follow these steps :

1. Make a new branch

Copy to Clipboard
2. Add a secondary remote coming from lootlocker gitlab repo then fetch it
Copy to Clipboard
3. Merge it
Copy to Clipboard

Then finally fix all conflicts and make sure it works in your local environment.

Important : most of the time, Lootlocker add and modify stuff in their databases and require migrations. Migrations are all stored in the migrations/ directory in go-backend. Migration will not automatically be done when deploying the new backend. You need to connect to the azure databases like explained in the Azure resources and copy paste execute new migration sql commands available in the _up.sql files.

Table of Contents