Am 12.02.2012 20:59, schrieb Wolfgang Rosenauer:
Am 12.02.2012 20:17, schrieb Ralf Lang:
Am 12.02.2012 19:59, schrieb Wolfgang Rosenauer:
I'm not deep into PHP app packaging but I'm working on an update for an existing app in server:php:applications right now.
Great. Which?
Roundcube Mail.
Is it a pear package or a traditional "unzip tarball" app?
unzip tarball app basically.
The app I'm working on is installing itself into /srv/www/NAME. Others are using /srv/www/htdocs/NAME.
Legacy stuff like horde3 installs itself to /srv/www/htdocs. phpmyadmin adheres to this schema too. If your existing app lives there, stick with it. If the app is currently not shipped with openSUSE and sufficiently modern to separate config from readonly "program" stuff, /usr/share/php5 may be a valid place too. Debian does it this way.
As Roundcube is not part of Factory I could move it but it's probably also not worth the effort if /srv/www/roundcube is ok, too. Personally, I'd like to reduce the number of default locations to /srv/www/htdocs and /usr/share/php5 but I'd like to hear feedback from others like chris wittmer. Maybe for now you should just do the update and you or I adjust the install path later.
Cannot answer that without looking at it.
For example it uses mod_rewrite wich is AFAIK not part of the default Apache config in openSUSE. So by using "a2enmod rewrite" in %post I could make sure it's enabled but not sure if we want that automatism?
I'm unsure on this and open for community decision. Does openSUSE usually enable apache modules when they are installed? With the horde stuff, I don't explicitly activate any apache modules. I am not even sure we should assume that users use apache2 and not lighttpd.
Should apps be enabled with their installation or via server flags?
If you ask me, they should only be accessible from localhost by default.
Good point. I'll consider this.
-- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org