Menu

Chef Supermarket

Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

View our collection of guides, documentation, and articles

Cookbooks
Advanced Options

Select Badges

Select Supported Platforms

Select Status

RSS

openfire (1) Versions 0.2.0

Installs Openfire Jabber server

Policyfile
Berkshelf
Knife 
cookbook 'openfire', '~> 0.2.0', :supermarket
cookbook 'openfire', '~> 0.2.0'
knife supermarket install openfire
knife supermarket download openfire
README
Dependencies
Quality 17%

Description

Install the Openfire Jabber server from source.

Requirements

The following Chef cookbooks should be installed:

  • java
  • database
  • postgresql

Supported Platforms

  • CentOS, Red Hat
  • Ubuntu (likely, but untested)

Database

This should still work using the built-in OpenFire database instead of using PostGreSQL. However this needs to be tested.

Attributes

All attributes are optional

Version

  • node[:openfire][:source_tarball]: currently defaults to openfire_3_8_1.tar.gz
    • This tarball will automatically be downloaded and installed

Installation

  • node[:openfire][:user]: the local user account to create and use to run the openfire process; defaults to openfire
    • also see node[:openfire][:group], which also defaults to openfire
  • node[:openfire][:base_dir]: the location on the file system to install openfire
  • node[:openfire][:config][:admin_console][:port]: Use your web browser to connect to this port while you are first setting up openfire. Defaults to 9090.
  • node[:openfire][:config][:admin_console][:secure_port]: Use your web browser to connect to this port after you have set up openfire for further configuration. This will require an https/SSL connection. Defaults to 9091.
  • node[:openfire][:config][:locale]: Defaults to en.
  • node[:openfire][:config][:network][:interface]: Defaults to nil (listen on all interfaces).

Database

  • node[:openfire][:database][:type]: currently only works with 'postgresql'. If you want to use the built-in database (untested), do not set this.
  • node[:openfire][:database][:password]: the database password for the Openfire user (required if database type is specified)
  • node[:openfire][:database][:name]: default openfire
    • also see [:database][:user], [:database][:host], [:database][:port], which have sane defaults

Usage

  • Optionally set the attributes mentioned in the Attributes section.
  • Add this to your node's run list: recipe[openfire], then run Chef.
  • Startup configuration is in the file /etc/openfire/openfire.xml
  • Java certificates are in the /etc/openfire/security directory.

New Installation

If you are configuring a new installation of Openfire, use your web browser to connect to your host, port 9091 (or whatever port you chose for node[:openfire][:config][:admin_console][:port] above). Run through the "wizard", and accept all defaults.

Import

If you are importing an existing installation of Openfire:

  • Optionally import the database
  • Within /etc/openfire/openfire.xml, right before the line </jive>, add the following: <setup>true</setup>.

Upgrading

This cookbook is not yet capable of automatically handling upgrades. To upgrade, follow the official instructions.

Download and untar into /opt/openfire. Then set symbolic links:
* ln -s /etc/openfire /opt/openfire/conf
* ln -s /var/log/openfire /opt/openfire/logs
* ln -s /etc/openfire/security /opt/openfire/resources/security

Also copy your plugins:
* rsync -av /opt/openfire_old/plugins/ /opt/openfire/plugins/

Dependent cookbooks

java >= 0.0.0
database >= 0.0.0
postgresql >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

Collaborator Number Metric 
            
0.2.0 failed this metric
Failure: Cookbook has 0 collaborators. A cookbook must have at least 2 collaborators to pass this metric.

Contributing File Metric 
            
0.2.0 failed this metric
Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a CONTRIBUTING.md file

Foodcritic Metric 
            
0.2.0 failed this metric
FC064: Ensure issues_url is set in metadata: openfire/metadata.rb:1
FC065: Ensure source_url is set in metadata: openfire/metadata.rb:1
FC066: Ensure chef_version is set in metadata: openfire/metadata.rb:1
FC069: Ensure standardized license defined in metadata: openfire/metadata.rb:1
Run with Foodcritic Version 16.3.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

No Binaries Metric 
            
0.2.0 passed this metric

Testing File Metric 
            
0.2.0 failed this metric
Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a TESTING.md file

Version Tag Metric 
            
0.2.0 failed this metric
Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must include a tag that matches this cookbook version number

Kurt Yoder Kurt Yoder

Details

Updated March 25, 2014 Created on

Supported Platforms

  • centos >= 0.0.0
  • ubuntu >= 0.0.0
  • redhat >= 0.0.0

License

Apache 2.0

Download Cookbook