![]() Most template or other behaviour configuration changes are best done viaĮxtensions, so use this hash to define the name of the extension and the path Refer to the comments there for full details create_htaccessĭefault: 0 db_mysql_ssl_ca_file db_mysql_ssl_ca_path db_mysql_ssl_client_cert db_mysql_ssl_client_keyĭefault: 250000 admin_login admin_email admin_realname admin_password Most of these correspond directly to settings in the localconfigĬonfiguration file. When set to true, the module will set up a cookie-cutter vhost for you that isĪcceptable for most standalone configurations.ĭefault: bugzilla::config Set this to false if you don't want to manage apache at all. Location defined by the upstream policy ( /usr/share/bugzilla).ĭefault: /usr/share/bugzilla manage_apache Undef to prevent the module from setting equivalency to the bugzilla If for some bizarre reason you disabled your SELinux, you can set this to You may tweak the flags passed to the cpanm command. If you must carry local changes thatĬannot be put into an extension, you can use your own repo location here.ĭefault: upstream bugzilla on github cpan_install_dir Where the local data should be kept (the data dir). Where the configuration files should be kept. Location where the bugzilla tree should be cloned.ĭefault: /usr/local/share/bugzilla config_dir ![]() Must match the tag in the bugzilla repository. If the database is exported, set the tag to be "caught" by the managingīugzilla version to install. If managing the db, is the db configuration exported? Whether to manage database setup and/or export (see more below). Whether to manage git installation (needed to clone the bugzilla repository). Repository, then downloading and installing a lot of CPAN modules required by The initial run will take a LONG time, as bugzilla will be cloning the git Latest release bugzilla::config::db_driver : 'mysql' bugzilla::config::db_host : 'x.x.x.x' bugzilla::config::db_name : 'bugs' bugzilla::config::db_user : 'bugs' bugzilla::config::db_pass : 'somepassword' bugzilla::apache_vhost_name : '' bugzilla::version : 'release-5.1.1' Initial run You should probably configure your database settings and hostname as well.ĭouble-check the latest version, too, as you will probably want to use the Without the above, the module will refuse to run. The minimal configuration bits that should go into hiera are: bugzilla::config::site_wide_secret : '' bugzilla::config::admin_login : 'administrator' bugzilla::config::admin_email : bugzilla::config::admin_password : 'somepassword' bugzilla::config::admin_realname : 'Bugzilla Administrator' It's expected that this module will be used with hiera, so the quickest way toĬonfigure it for your environment is to add it to your Puppetfile: mod 'mricon-bugzilla' Who will be the administrator and what the "site_wide_secret" should be (it'sĪ random string at least 64 characters long that will be used to hash client There are a few things you HAVE to set up to get going with Bugzilla, such as The modules do not clash with the rest of the distribution but provide the It installs them locally to a (configurable) location where It tries toĪvoid the dependency hell of depending on 3,000 perl packages provided by theĭistribution by relying on cpan-module installation scripts provided byīugzilla itself. Version 5 (though other versions will probably work, too). This module installs and configures Bugzilla ![]() Puppet module to manage Bugzilla installation and configuration.
0 Comments
Leave a Reply. |