Closed Darthyoda714 closed 6 months ago
Assumptions:
First iteration is just to have the option to write to multiple HostSecurity files when the time comes to update them.
In terms of merging the HostSecurity data back in to the user db, it is probably safe to just use one, as right now we are really only grabbing the UID.
Things get a bit more complicated when also looking into issue #91 - since that brings in the concept of tracking a user's login history. The current solution for that issue is to add another column to the user db named "last_login" - which is populated via scraping the log file. With multiple servers now:
For the logging/pruning of users, rather than a log of each "last login", it would be simpler on the schema to add not only the "last_login" field, but also "last_server" field.
Envisioning the configuration file having entries as such:
[server1]
name = CaliSW
security_file = C:\Program Files\Run8Studios\CaliServer\Run8 Train Simulator V3\...etc.
log_file = C:\Program Files\Run8Studios\CaliServer\Run8 Train Simulator V3\...etc.
[server2]
name = SouthEast
security_file = C:\Program Files\Run8Studios\SeServer\Run8 Train Simulator V3\...etc.
log_file = C:\Program Files\Run8Studios\SeServer\Run8 Train Simulator V3\...etc.
This is currently being tested on branch #105
This has been addressed in branch #108
The ability for the bot to be able to handle multiple host security files on the same computer for servers hosting multiple R8 regions on the same hosting machine.