User.ini and Php disabled functions Issues in Magento 2 deployment

kganeshkumar12

@aaPanel_Jose
Hi,
I have a magento 2 website and while deploying it into aapanel,
There are issues and I have mentioned them below

Issue 1
default open_basedir=/www/wwwroot/aapaneltest.excrin.com:/tmp:/proc in user.ini causes error.
That issue can be solved by modifying the open_basedir value to /www/wwwroot/aapaneltest.excrin.com:/tmp:/proc:/etc
Im afraid that allowing "etc" folder may become a security issue.
can u or anyone comment on exposing etc folder is a right approach or it should not be done?

Issue 2
In Php manage popup,
In Disabled functions tab, there are lot of predefined disabled functions.
on that, "phpenv" causes error in magento 2.
deleting that "phpenv" from that tab, solves the issue to let magento run
Since there are no dicumentation and no hints mentioned atleast in the popup along with each disabled functions, Its hard to distinguish which functions are used to what kind of purpose, which functions should not be removed and which will be a security threat.
Can you or anyone comment on the purpose of those listed functions?

aaPanel_Jose

kganeshkumar12
First of all, thank you for your feedback.
1,
You'd better specify the folders that need to be cross-site. It is not safe to use /etc directly.
As your settings:
/www/wwwroot/aapaneltest.excrin.com:/tmp:/proc:/etc
change into:
/www/wwwroot/aapaneltest.excrin.com:/tmp:/proc:/etc/you/need/access/this/folder

2,
I think it can be achieved, but it is not a matter of urgency. Let us record it first and then arrange the time later.