Intending to package a web application
Hi,
When inspecting the openx's installation proccess ([1]) in order to
begin packaging it, i've found that most of its paths (except for the
cache location) are not configurable: it expects to have all the files
(configuration related, static content, dynamically interpreted content
and include files) mixed in subdirs below a common directory. This
doesn't seem to be in-line with the FHS, would it be right to distribute
the files among /usr/share/appname and /usr/share/appname/www and have a
unique web accesible directory at /usr/share/appname/www with symlinks
to the parent directory?
Moreover, most of the initial configuration is made via web after the
files' deployment, accessing the web application and following a
configuration wizard in an interactive way. When the proccess is done, a
main configuration file is written to the web accesible directory with
the selected settings. I've read at [2] that you should use the
application's language include construction to put the configuration
file in /etc/appname, how could this be done in this case, when the
configuration file is not present in the package and is generated after
the package is installed? Maybe with another symlink
at /usr/share/appname/www and allowing the web application to write
to /etc/appname?
Thanks a lot,
Federico
[1] http://www.openx.org/docs/2.8/adminguide/Preparing+for+an
+installation
[2] http://webapps-common.alioth.debian.org/draft/html/ch-issues.html
Reply to: