[ previous ] [ Contents ] [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] [ 6 ] [ next ]
While not strictly necessary, it's highly recommended that package maintainers use pre-existing tools to aid in packaging web applications. This centralizes the effort not only for the packageers themselves, but also for translators and results in a much more consistant feel for users of web applications:
dbconfig-common is an implementation of the "best practices for database applications" draft, which provides debian packagers with an easy, reliable, and consistant method for managing databases used by debian packages.
dbconfig-common can:
support mysql and postgresql applications
create databases and database users
access local or remote databases
upgrade/modify databases when upstream changes database structure
remove databases and database users
generate config files in many formats with the database info.
prompt users with a set of normalized, pre-translated questions
do all the hard work automatically
work for package maintainers with little effort on their part
work for local admins with little effort on their part
comply with an agreed upon set of standards for behaviour
do absolutely nothing if it is the whim of the local admin
perform all operations from within the standard flow of debian package maintainance (no additional skill is required of the local admin)
webapps-commonprovides a centralized set of tools and procedures
for configuring web applications, webserver extensions, and other packages
related to the world of web applications. Details of this package, and it's
implementation can be found in the webapps-common
developer's guide. The webapps-common package may be
used instead of registering applications directly with the webserver, as
described in Registering and unregistering an application with web
servers section.
[ previous ] [ Contents ] [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] [ 6 ] [ next ]
Webapps Policy Manual
Revision: DRAFT-1.9