Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.php > #12259
| Newsgroups | comp.lang.php |
|---|---|
| From | Moon Elf <moonelf@moonelfsystem.net> |
| Subject | Re: where to put a php library shared between (virtual) sites. |
| References | (1 earlier) <b09oq8FmkvvU1@mid.individual.net> <e8Snt.25581$cs.20058@newsfe03.iad> <knppbp$2n7$2@news.albasani.net> <b0br90F5p9rU1@mid.individual.net> <knqlcu$ruh$2@news.albasani.net> |
| Message-ID | <slrnlas2te.nmd.moonelf@sigtrans.org> (permalink) |
| Date | 2013-12-15 20:06 +0000 |
| Organization | SunSITE.dk - Supporting Open source |
On 2013-05-25, The Natural Philosopher <tnp@invalid.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@mid.individual.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.
Back to comp.lang.php | Previous | Next — Next in thread | Find similar | Unroll thread
Re: where to put a php library shared between (virtual) sites. Moon Elf <moonelf@moonelfsystem.net> - 2013-12-15 20:06 +0000 Re: where to put a php library shared between (virtual) sites. Jerry Stuckle <jstucklex@attglobal.net> - 2013-12-15 15:12 -0500
csiph-web