Thulium

Sounds familiar, I made these packages to get 'a feel' for making software packages in general (I know, they probably are not good enough to be included in Debian or any other OS, but they have been good enough for my personal stuff and at work). Build automation should be easy once you built the first docker image. You might want to check out Drone (https://drone.io) for a Docker integrated CI/CD solution. I use it to build some Docker images for my own personal systems.

There is, check trinityserver-database3.3.5, it also has a small script that will setup a db server :-) I split that off on purpose, so it's possible to run multiple trinitycore instances sharing the same DB without lugging around multiple copies of the database. The build script does some magic to copy all the SQL files out of the github source of TC. Nice work! It's actually quite well suited to run in docker, all of the dependencies can be just folded in one neat little container, and (not sure if you can) should you statically link the binaries, you can probably even cut out most of the surrounding Debian OS. Oh, one last thing, the dependencies section in the build files is only build-time dependencies, you can't compile something that is an SQL client without the required header files ;-) runtime dependencies are in the DPKG definition at the bottom. Do note BTW that I will not port the packages to Debian 11 next year, as I no longer play WoW nor run a server myself!

The setup_database.sh script is in _trinitycore-database3.3.5_ only, as the script relies on the SQL files also distributed using that package. But the database package is _not_ installed automatically, due to the fact that you might want to use a dedicated database server.

You can still use it without systemd, the package places some stuff in /etc/systemd/system, which only does stuff as long as systemd is in your docker images :-) So you can do one of 3 things (the third is only for completeness sake, you should pick 1 or 2): 1. Add the package as-is to your docker, ignore the systemd config (it has no dependencies on systemd, so you can install it in an image without systemd) 2. Make your own build, be sure to copy the repo and remove the systemd stuff from trinity-server3.3.5.files/B_DEBIAN (this is the 'control' directory for dpkg). You can also see the things I do to start the server. 3. Run the containers privileged, systemd is weird that way... (don't actually do this)

Hey, Did you install the trinitycore-database3.3.5 package as well? It's supposed to be in /opt/trinitycore/bin and that is added to your PATH variable (hence why you don't need to type in the whole path). The database package is not installed automatically, in case you want to run it on a different server.

Hi all, It took me a whole lot some time to prepare my Debian 10 buildserver, but I finally got around to do so. Please find new packages up in the repo! I have updated the TS with the new paths. Please note that builds for Trinitycore on Debian 9 have been broken for a month or 2 because some of the build dependencies changed to versions that are not available in Debian 9 (for example SSL). Also, I'm winding down on my own server as I don't play WoW any more. I will keep compiling the packages for the forseeable future, but I will not port them to Debian 11 (slated for ~Q2 2021). Please find all the scripts and recipes in the TS to roll your own :-)

The password it asks is the one for the database server root, the generated password is for the TC databases, so you probably installed a DB server and secured that beforehand. Most default installations of MariaDB on Debian don't request a password if you are logged in as root on the system and run mysql commands. Buster packages are coming up soon, just a few more days until it's (long awaited) release...... :-)

It took me some time to set this up properly ;-) I'm glad it works well :-) About the missing config keys, that's correct, the config files are still the same (from the ones I created back then) and are not updated (as it requires me to reconfigure them each time a new key is added). Good thing for us is that the software doesn't care about missing keys and will assume a sane default value. The best/easiest solution would be to 'port' the configuration included in the packages to a fresh config file. Same goes for the warnings, the server will run just fine, but this is only because the DB is newer then the code, the other way around could be problematic, as you'd be referring to DB objects that don't exist for scripts that need 'm.

Hey, I (very) recently updated the repo to use https, if you have issues downloading the packages, make sure you have apt-transport-https installed. When installing the server it does not automatically install the database packge, this allows you to use a different machine for the DB :-) (e.g. you already have a tuned DB server running). You can always install the DB package on the same host as the server package. It will pull in a mariadb-server as well. Not sure about the DB errors... The only check you can do is see if all trinitycore-*3.3.5 packages are of the same day, I just did and it seems the DB package is about 12 days newer. I'll need to check my buildserver why it isn't building the others. EDIT: found the issue, build was stuck on installing a dependency :-) just started it up again, expect new arrivals in ~2 hrs

Well, in that case, roll your own ;-) https://github.com/Thulium-Drake/trinitycore-recipes

psst, if you manage to get it working, don't forget to make a post on how you did it :-) help someone else help themselves too ;-)

The documentation has everything you need: https://trinitycore.atlassian.net/wiki/spaces/tc/pages/2130077/Installation+Guide

If you downloaded the Windows archive, you're going to have a hard time running the software.. Can you run 'file worldserver.exe', it should say something like: worldserver: ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=9c04eb9ccf1cf2a97498f2b8aa4254aba44600ff, not stripped If you're running into issues with compiling and installing the software, have a look over here:

Shameless plug: All the work you mention has already been done there ;-)

Hi all, For those that are still using my packages, please note that the package name has changed! It's now suffixed with '-en', and I have put in place some scripting that will clean up old builds (as it was frequently clogging up my repo server). The name has changed due to me using the build script for other stuff as well and I want to avoid naming collisions with other software that resides in the repo. I have updated the TS :-) TL;DR: use trinitycore-server3.3.5-en, trinitycore-database3.3.5-en and trinitycore-tools3.3.5-en now.