Ulysses Stuff > Suggestions
MySQL server
Killers:
I would like ULX to support MySQL servers for the ban list and users and other files...
I just have a thing for MySQL :P
Megiddo:
Have you seen our script UBan? It's a MySQL ban list that can be shared across multiple servers. As far as users list, I understand why you would want something like that (we have our servers hooked up to this forum to grab the user list based off the forum user group, it's pretty neat). Still, I don't think there's a high enough interest in something like this to make it worth-while.
spbogie:
MySQL support for users is not likely to be a feature added to the official build, however it would not be overly difficult to create a ULib module to query users from an SQL database. As for bans, there is UBan which uses an SQL database to store ban info for use accross multiple servers, but it would work just as well for a single server if that's all you wanted it for. Using UBan you would have to use the different commands to ban people, but if you didn't want anyone to use the default ones for files you could simply deny access to all admins to that, and if want could even rename the commands int he Lua scripts.
I'll not have any time to create such a module for who knows how long, but I would gladly help point you in the right direction.
Edit: Bah, Meg got here first *shakesfist*
Killers:
So Uban would not load the ulx bans file into the database automatic and automatic add entries to the database?
spbogie:
UBan uses different ban commands, so you would essentially have two seperate ban datablases, the default flatfile one which Source uses, and "ulx ban" works off of, and the MySQL database for those done with UBan. Your existing bans would not be transfered over, and any new bans made with the default commands would still end up only in the flatfile, but you could force your admins to use the UBan commands so that all new bans would go to the SQL server, and would just have to manually enter any bans in the default file.
Navigation
[0] Message Index
[#] Next page
Go to full version