Some ideas:
- sudo should be used only to execute action that require root access. It should not be used for anything else. It will very probably be clamped to the few commands already used or even removed completely as soon as we will swap on suExac scheme.
- if you have to access to a file from the panel, this file must be setup to have apache as owner or to be in the apache group by module installer.
- Be carefull with OS specific pathes and files : do not forget that Sentora must be able to run on Centos6 and 7, on Ubuntu 12 and 14, with 32 & 64b. (I did not found /etc/csf on my server, U14)
- sudo should be used only to execute action that require root access. It should not be used for anything else. It will very probably be clamped to the few commands already used or even removed completely as soon as we will swap on suExac scheme.
- if you have to access to a file from the panel, this file must be setup to have apache as owner or to be in the apache group by module installer.
- Be carefull with OS specific pathes and files : do not forget that Sentora must be able to run on Centos6 and 7, on Ubuntu 12 and 14, with 32 & 64b. (I did not found /etc/csf on my server, U14)