Re: Using a PEAR-installed web application on multiple vhosts
| From: | Christian Weiske | Date: | Sun, 29 Aug 2010 11:39:56 +0000 |
| Subject: | Re: Using a PEAR-installed web application on multiple vhosts | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-53733@lists.php.net to get a copy of this message | ||
Hi again,
> Up to now I thought that just symlinking the user's vhost
> directory /home/username/www/bookmarks.example.org/ can be symlinked
> to $pear_www_dir/application/, making all www-relevant files
> available in the vhost.
> Unfortunately, this does not allow the user to configure the
> application by creating a config file in the vhost directory.
>
> Configuration is the central problem here: How does the user configure
> the application in each vhost?
Another idea to please multiple instances of the same application on
the server is to do the following:
- symlink vhost dir to the app www dir
- create a vhost-dirname-$appname-config.php file in the parent
dir of the vhost,
i.e. /home/user/www/example.org-semanticscuttle-config.php
for /home/user/www/example.org/ that symlinks
to /usr/share/pear/www/semanticscuttle/
Now the application checks if that file exists and loads it as config
file. That way, one user may have multiple instances of the same
software running.
The only open problem is database upgrades through pear, because
virtually unlimited instances of the application database may be
running on the server. No way for PEAR to know about some or all of
them.
--
Regards/Mit freundlichen Grüßen
Christian Weiske
-=≡ Geeking around in the name of science since 1982 ≡=-
Attachment: [application/pgp-signature] signature.asc
Attachment: [application/pgp-signature] signature.asc