I am trying to move over from VestaCP to Ispconfig and am having a real issue with open_basedir. I use Concrete5 for websites and put the main APP in a directory (lets say /var/www/concrete5-8.5.4) then I simlink concrete-stable to that directory. The reason is if I update to concrete5-8.6, all I have to do is change the simlink and it updates for all the site. In the website directory (/var/www/clients/client1/web2/web) I put a simlink to concrete->/var/www/concrete-stable. This has worked well for years, but now I just can't seem to get past the open_basedir. open_basedir does have a reference to /var/www/concrete-stable I even tried adding another /var/www/concrete5-8.5.4 (directly to the app) but it still give the same error that the directory is no in the open_basedir. I used open_basedir on Vesta and never had this issue. Help! Please!
Thanks Th0m. So if that’s the definitive answer then it’s not going to work. Because the concrete5 config is very much like the Typo3 where only part of the application is outside the main web directory. I though that www-data user would have privileges to read outside the web2:client1 users directory. Would there be a way to do this by amending the www-data permissions. Oh wait! I missed the part about bind mount. I’ll give that a try.
You could try the bind mount, but if that doesn't work it will be difficult. Maybe you can run it like PHPMyAdmin is used by setting a global alias?
Yes, but just like the link you sent, concrete5 is not all in the one folder. The config and some other settings would me in the root website folder. The main app is outside. I could just stick the whole thing inside each root website but that takes extra space and updating is more work.
