Re: publicweb role
| From: | Pierre-Alain Joye | Date: | Sat, 06 Sep 2003 18:59:21 +0000 |
| Subject: | Re: publicweb role | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-21120@lists.php.net to get a copy of this message | ||
On Sat, 06 Sep 2003 09:18:49 -0400
Greg Beaver <greg@chiaraquartet.net> wrote:
> Hi Tomas,
>
> I think we have a different understanding of what publicweb is, here
> is a few examples.
>
<snip>
> Neither one of these examples is a standalone application, but both
> can be used by applications. So, I don't think publicweb has anything
> to do with applications, at least not any more than any other role
> does.
You are not wrong neither Tomas. 'App' is a general name. Maybe not
well named, remind plugin/addons/subpackages discussions ;-).
However a publicweb can be considered as a app data. As web
datas and with many destination folders, one per host. Each host can be
see as an user.
The only difference between a custom app data and the webrole is that
webrole should be normalized. For instance, the javascript files should
follow the pear naming convention but lowercased.
The same applies for images or static html pages. Each application may
allow default path override. Or we can define some default global datas
and user datas. The installer should not overwrite user datas.
What about CLI application?
The same features are required. Global data and user data:
~./.pear/.xml/xslt_wrapper/ for the user datas (i.e. custom config
files)
{PEAR_CONFIG_SYSCONFDIR}/.xml/xslt_wrapper for the default/global datas
a little summary of my thought ;)
pierre