FUDforum: comp.lang.php » where to put a php library shared between (virtual) sites.

Home » Imported messages » comp.lang.php » where to put a php library shared between (virtual) sites.

Show: Today's Messages :: Polls :: Message Navigator

Re: where to put a php library shared between (virtual) sites. [message #184219 is a reply to message #181701]

Sun, 15 December 2013 20:06

Moon Elf
Messages: 6
Registered: December 2013

Karma:

Junior Member

On 2013-05-25, The Natural Philosopher <tnp(at)invalid(dot)invalid> wrote:
> On 25/05/13 14:05, J.O. Aho wrote:
>> On 25/05/13 09:31, The Natural Philosopher wrote:
>>> On 24/05/13 23:49, Sanders Kaufman wrote:
>>>> "J.O. Aho" wrote in message news:b09oq8FmkvvU1(at)mid(dot)individual(dot)net...
>>>> > On 24/05/13 16:20, The Natural Philosopher wrote:
>>>>
>>>> >> But where is the most normal place, that e.g. anyone might EXPECT to
>>>> >> find them?
>>>> >
>>>> > There is no "most normal" place. You should document the location, one
>>>>
>>>> Actually, a named server is the industry standard - just like with
>>>> database servers, static content servers, web servers and app servers.
>>>> (e.g. db.kaufman.net, static.kaufman.net, www.kaufman.net,
>>>> apps.kaufman.net)
>>>> I think it's even codified in the latest ISO9xxx standard.
>>>>
>>> Thanks for that. A most interesting idea. But wouldn't that make them
>>> PUBLICLY accessible to anyone on the net?
>>>
>>>
>> Sure, Sanders example here would require you to have a copy in each
>> virtual host, with other words what you already done.
>>
>> Using the include_path option in php.ini, then if it's a global
>> php.ini the modules would be accessible by all vhosts on that server,
>> if you sites has individual php.ini (as you can have in a suExec
>> setup), then those modules would only be accessible by those vhosts
>> with the right php.ini.
>>
> I suppose another example would be to hard link the files to 'copies' in
> each vhosts directory.
>
> And make em readonly :-)
>
>

LAMP installation : use /usr/local as the php5.5.6 build will use
--with-config-file-path=/path/to/php.ini or /usr/local/lib/php.ini

Then if you're not an admin run your server above port 1024 e.g. 8080 and
load from a shared object file somewhere, then load php files in a user's
public_html directory. This means you compile your own apache and php
installation.

ME
--
Member of the DR rogue circle.
Search and you will find.

Report message to a moderator

[Message index]

		where to put a php library shared between (virtual) sites. By: The Natural Philosoph on Fri, 24 May 2013 14:20
		Re: where to put a php library shared between (virtual) sites. By: J.O. Aho on Fri, 24 May 2013 18:11
		Re: where to put a php library shared between (virtual) sites. By: Sanders Kaufman on Fri, 24 May 2013 22:49
		Re: where to put a php library shared between (virtual) sites. By: Jerry Stuckle on Fri, 24 May 2013 23:19
		Re: where to put a php library shared between (virtual) sites. By: The Natural Philosoph on Sat, 25 May 2013 07:31
		Re: where to put a php library shared between (virtual) sites. By: J.O. Aho on Sat, 25 May 2013 13:05
		Re: where to put a php library shared between (virtual) sites. By: The Natural Philosoph on Sat, 25 May 2013 15:29
		Re: where to put a php library shared between (virtual) sites. By: Moon Elf on Sun, 15 December 2013 20:06
		Re: where to put a php library shared between (virtual) sites. By: Jerry Stuckle on Sun, 15 December 2013 20:12

Previous Topic:	Open Portal - web portal software
Next Topic:	YouTube script quits displaying "Tags" info

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Jul 11 23:44:00 GMT 2024

Total time taken to generate the page: 0.05308 seconds