documize #9

Description

From the Documize website:

Documize creates the Enterprise Knowledge Backbone by unifying docs, wiki, reporting and dashboards.


Documize

Documize creates the Enterprise Knowledge Backbone by unifying docs, wiki, reporting and dashboards.

composition + coordination + discovery + distribution + workflows = faster business outcomes

Documize Homepage

Usage

To deploy Documize, you will need to accompany it with a MySQL database.

Suppored databases:
MySQL
PerconaDB
* MariaDB

We can accomplish this using Juju as follows:

juju deploy documize

juju deploy mysql

juju relate mysql documize

Authors

Copyright

License

  • AGPLv3 (see LICENSE file)

Configuration

fqdn
(string) FQDN of documize server (for nginx config), defaults to "_"
_
port
(int) Nginx listen port
80
host
(string) listen address
127.0.0.1
package_status
(string) The status of service-affecting packages will be set to this value in the dpkg database. Valid values are "install" and "hold".
install
extra_packages
(string) Space separated list of extra deb packages to install.
install_keys
(string) List of signing keys for install_sources package sources, per charmhelpers standard format (a yaml list of strings encoded as a string). The keys should be the full ASCII armoured GPG public keys. While GPG key ids are also supported and looked up on a keyserver, operators should be aware that this mechanism is insecure. null can be used if a standard package signing key is used that will already be installed on the machine, and for PPA sources where the package signing key is securely retrieved from Launchpad.
install_sources
(string) List of extra apt sources, per charm-helpers standard format (a yaml list of strings encoded as a string). Each source may be either a line that can be added directly to sources.list(5), or in the form ppa:<user>/<ppa-name> for adding Personal Package Archives, or a distribution component to enable.