I've created a Service Plan Add-On for Typo3. It just extends the default open_basedir path.
If i create a new subscription and selected the Service Plan Add-On "Typo3". It works fine:
# grep typo3 *
php_admin_value open_basedir "/var/www/vhosts/aaa.de/httpdocs/:/tmp/:/usr/local/share/typo3"
php_admin_value open_basedir "/var/www/vhosts/aaa.de/httpdocs/:/tmp/:/usr/local/share/typo3"
php_admin_value open_basedir "/var/www/vhosts/aaa.de/httpdocs/:/tmp/:/usr/local/share/typo3"
php_admin_value open_basedir "/var/www/vhosts/aaa.de/httpdocs/:/tmp/:/usr/local/share/typo3"
but if i use a already created domain and add the service plan add-on "typo3" to it, a new httpd.include
is generated, but without the new open_basedir. maybe this is a bug?
thanks,
patrick
If i create a new subscription and selected the Service Plan Add-On "Typo3". It works fine:
# grep typo3 *
php_admin_value open_basedir "/var/www/vhosts/aaa.de/httpdocs/:/tmp/:/usr/local/share/typo3"
php_admin_value open_basedir "/var/www/vhosts/aaa.de/httpdocs/:/tmp/:/usr/local/share/typo3"
php_admin_value open_basedir "/var/www/vhosts/aaa.de/httpdocs/:/tmp/:/usr/local/share/typo3"
php_admin_value open_basedir "/var/www/vhosts/aaa.de/httpdocs/:/tmp/:/usr/local/share/typo3"
but if i use a already created domain and add the service plan add-on "typo3" to it, a new httpd.include
is generated, but without the new open_basedir. maybe this is a bug?
thanks,
patrick