I love how much DirectAdmin can be customized. But the lack of documentation and just everything scattered every where is the part that just REALLY gets on my nerves.
Like...
Why can some things be turned off with a commands.deny or never_command list but other things can't? Where do we find this list of things that can be turned off here?
Other things have to be disabled at the reseller (or admin) level. You can control these by making modifications to /usr/local/directadmin/data/users/%reseller%/skin_customizations/evolution/files/menu-v4.json or is it menu-v2.json? Once upon a time it was menu-v2.json, now it's menu-v4.json. WHAT DIFFERENCE SHOULD IT MAKE! Just call the damn file menu.json and be done with it! But if you don't adhere to the strictest of JSON layouts, it won't be read anyway. Or maybe it's not being read because it should be menu-v6.json? How the hell are you supposed to know what the name of the file is suppose to be?
Can we please standardize some of this crap!
And if something has to be disabled in the menu-v\d+.json file then you can't enable it for just one user... No... it has to be enabled for ALL of the accounts under that reseller (or admin). That's why I prefer commands.deny, it can be per user. But only some things can be listed there. But good luck figuring out what can and can't be listed there!
There has to be a better way of doing all of this. And no, I don't want to log into 50 DirectAdmin admin panels and set all of this up. I actually don't want to log into the admin panel ever if I can keep from it. All of this should be doable from the command-line, where either a series of commands can be pushed out to all 50 servers all at once or some file structure (I'm looking at you menu-v\d+.json!) can be distributed to each server and bringing those settings to match the parent server.
Sorry if I offended anyone. I'm on a bit of soapbox. I've spent all day trying to figure all of this out and I'm a little pissed off at the moment.
