Jyri Virkki wrote:
> James Gates wrote:
>
>> 4.5.2. Imported Interfaces
>>
>> NAME STABILITY NOTES
>> PHP5 Uncommitted PSARC/2007/168
>> Apache2 Uncommitted PSARC/2004/676
>>
>
> The apache2 import should really be PSARC/2007/586 as that is the one
> available in Nevada/OpenSolaris, where this case is headed (2004/676
> is the old apache 2.0 which doesn't exist anymore).
>
>
>
OK, thanks for pointing this out, I will update the 1-pager to this
effect.
>> 4.5.3. Exported Interfaces
>>
>> NAME STABILITY NOTES
>>
>> SUNWphppgadminu committed Usr component
>> SUNWphppgadminr committed Root component
>> Files Layout within pkg uncommitted
>>
>> One config file is delivered here:
>> /etc/phppgadmin/config.inc.php
>>
>
> Not clear to me why the entire file layout (under
> /usr/postgres/phppgadmin) should be a public interface. Do you intend
> to document & supports users to change/tune/reference the content
> there?
>
> Without looking at it in detail, seems like everything below
> /usr/postgres/phppgadmin is project private and
> /etc/phppgadmin/config.inc.php is the public interface, no?
>
> The top path "/usr/postgres/phppgadmin/" does need to be an
> interface as well since users need to hardcode that path into their
> web server configuration. But making everything under it private seems
> to make sense (then you can update the version without worrying if any
> implementation files move around).
>
>
yes, the file lay out could change at anytime and we don't guarantee
or document
the content structure. This should probably then be classified as
"project private" as you mentioned
instead of "uncommitted". yes, the /etc/phppgadmin/config.inc.php is
public interface and I will add
another line to explicitly clarify this.
>
>
>> One has to setup the webserver to activate this.
>>
>
> This seems to be the key missing bit here.
>
> Have you evaluated the possibility delivering an additional
> apache2-specific connector package which enables it (probably by
> delivering appropriate apache2 configuration into
> /etc/apache2/2.2/conf.d/) if the package is installed? That would
> allow documenting a one-line procedure setting up phpPgAdmin
> ("pkg install SUNWphpphadmin SUNWapch22-phppgadmin").
>
> Merely delivering some php files doesn't add much value. Anyone could
> download the phpPgAdmin tarball and untar it into their docroot about
> as easily as typing "pkg install SUNWphpphadmin". The opportunity for
> real value-add for OpenSolaris here is if you can also deliver
> something that "just works".
>
>
I did take a look into this and found that we don't need another
predefined config file for phppgadmin
comparable and similar to config modules in /etc/apache/2.2/conf.d. We
bundle sun specific man page
for phppgadmin where we describe how to configure phppgadmin with apache
with fairly simple couple
of lines change in httpd.conf file.
I am attaching the updated 1-pager.
-thava
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: phppg1pg.txt
URL:
<http://mail.opensolaris.org/pipermail/opensolaris-arc/attachments/20080516/db7ca34f/attachment.txt>
