next »

[DangerMouse]

Hi guys,

I'm certain that this is well within the realms of experience of those here -I currently have a dedicated server with a couple of hundred domains hosted, managed via a Plesk control panel.

Security policy on the server means that each domain / site cannot access files outside of its own vhost, but I'd like to create a shared location for certain PHP scripts. Any ideas?

I guess its possible over a HTTP request if I can't do it any other way, but I'm ashamed to say I'm not sure how to execute a script thats come from file_get_contents() or similar.

Tips appreciated! As I said I'm certain plenty of distributed apps have been written here

DM

[perkiset]

Shared scripts or shared variables?

Shared scripts: ssh into the box. Make a directory that you will put shared stuff into. I use /www/sites/lib. Then in the directories where the site specific scripts are, symbolically link to them. (hard links are fine as well, but they are less obvious). So in /www/sites/lib you'd have a script called shareMe.php. In /www/sites/targetSite/scripts you'd type

ln -s /www/sites/lib/shareMe.php .

and you're good to go. Probably 70% of my scripts are used this way.

[perkiset]

Btw don't use dynamic code with an eval and file_get_contents unless there is absolutely no other way to do it.

[DangerMouse]

Fair point on the dynamic code - I would prefer the sym link route too.

Just tested it out and it seems to be failing - but its failing silently so I can't figure out the problem - if permissions prevented a symlink from working would the server throw an error on creation via the CLI?

DM

[DangerMouse]

Quick update - I've verified that the sym link works just by hitting vi at command line, but it still doesnt work through Apache?

This is looking like an Apache conf thing to me now?

DM

[perkiset]

You MAY need to add FollowSymLinks to your apache config, but more likely the underlying files don't have the right permissions for the Apache user (often www or nobody). Try setting the permissions to 777 and see how it goes. There's not reason why Apache can't read it really.