Also: is it correct that I need both aw-core and aw-server to only create a listening server with database-storage if I don’t want to track activity on that server itself? With some modifications I was able to compile those two components on FreeBSD but I have trouble with some of the other ones. So I would prefer not to invest more time if it isn’t necessary in this Use Case.
We have not tested it at all on FreeBSD so if something doesn’t work you are on your own, but yes you are correct that only aw-server and aw-core should be needed. There’s nothing platform specific in aw-core and aw-server so technically it should be able to run on FreeBSD, but my guess is that there are likely a few issues just as when we ported the project to windows and mac.
I am trying to use the aw-server component with a MySQL backend but cannot seem to find out where to configure this. I would prefer to use an .ini file, but where would that need to be placed with which settings?
The only official database we have official support for is peewee (a SQLite wrapper). We have experimental support for mongodb and raw SQLite (which has some performance improvements over peewee, will hopefully be default later), but we do not recommend using these either.
You could of course code support for MySQL/Postgres yourself (see the aw-core/aw_datastore files), but that would probably take 10+hrs to develop for someone with python and SQL experience.