Why not to use plugins as package items feature for this?
Because I have my plugins written long time before there was an option for it, and one plugin has several ACLs.
Example:
Backup plugin in package1 has only local feature, in package2 local + ftp.
Do you mean environment variables?
Not only. We have some PHP/bash scripts implemented to print data from outside scripts.
Like literally printing output of php script/bash script or simple reading file (not plugins)
Already there in "Customize Evolution Skin"
Custom CSS, Custom JS, Custom HTML.
Like embedding video tutorials, boxes "show more", tooltips, URLs to KB with specific doc.
Like, the old one, skin I mean, gives us a lot of control over how the frontend and backend of it will look like and work. With Evolution I feel like it's cloud based dashboard with little to no customization (I don't count colors or images) while it's self hosted panel without ability to fully customize the frontend and backend for it.
I love the new Evo skin, but without being able to edit it to fit my needs I simply cannot use it without doing some JS hacks to catch elements and replace a lot of stuff. But it still won't be enough without being able to use PHP/BASH to print other things I want.