include new table in main schema, since this plugin is part of Koji itself
clean up and expand the docs for this plugin
refactor query_from_db() into handle_db_msgs()
* fix lock error cases
* only delete messages from queue if we successfully send them
* handle test_mode
allow test_mode to exercise db queue via test_mode_fail setting
Make the Server HowTo SELinux instructions simpler and easier to read.
Describe each step for users to copy-and-paste.
Use semanage and restorecon instead of chcon in order to make the
changes persist across relabling operations.
Only recommend httpd_can_network_connect_db=1 if the user is using a
TCP/IP connection to PostgreSQL. If koji-hub is using a local Unix
socket connection, Apache does not need this setting.
Rewrite the PostgreSQL authorization instructions in the Server HowTo
guide.
Provide two complete examples: the "all-in-one localhost" option, and
the "separate postgres over the network" option. This reduces the
decision trees and makes it easier to copy and paste the entire
pg_hba.conf file. Explain what each mystery setting does and link to the
PostgreSQL documentation.
Only set listen_addresses to "*" if we need it, and turn it off if we
don't.
Simplify the instructions so that the user only restarts the postgresql
daemon once.
Clarify that koji-web does not need DB access, and the hub is the only
service that requires direct DB access.
Remove the example of authorizing the apache system user, because that
implies that the admin must run a series of complicated GRANT
instructions to allow both koji and apache to write to the DB. Just
grant the koji user full trust access for simplicity.
Prior to this change, Google Chrome's SVG renderer did not display "Hub"
centered in the Koji structure diagram.
Re-do the "Hub" text in the diagram so that it is centered in Inkscape,
Firefox, and Chrome.
