tabarra
Suggestions: Admin Manager
#1 -- Make it so admins of a certain amount of permissions cannot edit those with higher amounts of permissions. For example, someone with 5 permissions shouldn't be able to edit someone with 10 permissions. Perhaps have a toggle where in addition to managing admins, there can be an additional one granting access to managing permissions for said admins. Could reduce the amount of abuse.
#2 -- Sort "Admins" based on their access levels (highest to lowest) in the admin manager.
#3 -- Design a template system for big servers where we can select from drop-down permissions that all one rank should have in the server.
#4 -- Long-term idea, for communities and organizations that run multiple of the same style server, perhaps have a way to connect them through an API so you can add one user to say, three different servers for example.
Item 4 is ready.
You just have to run fxserver multiple times with different profile names, and the admins will be synced.
Item 4 is ready. You just have to run fxserver multiple times with different profile names, and the admins will be synced.
So this is great if they're all on the same machine, but not ideal for large organizations that run on separate dedicated environments, such as us for example.
Kinda of an edge scenario.
Set one server to be the "master one", and then configure a tool like rsync to auto sync the admins.json from that server to the other ones.
Should work.
Kinda of an edge scenario. Set one server to be the "master one", and then configure a tool like rsync to auto sync the
admins.jsonfrom that server to the other ones. Should work.
Hmm. You actually just gave me an idea of keeping it in sync using Git.