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.

Select Badges

Select Supported Platforms

RSS

liquid-feedback (2) Versions 1.1.0

Set up liquid feedback system

Berkshelf/Librarian
Policyfile
Knife
cookbook 'liquid-feedback', '~> 1.1.0'
cookbook 'liquid-feedback', '~> 1.1.0', :supermarket
knife cookbook site install liquid-feedback
knife cookbook site download liquid-feedback
README
Dependencies
Quality 33%

Description

beta

Sets up a liquid democracy tool: LiquidFeedback (http://liquidfeedback.org)

Based on Lua and Postgresql

Requirements

Cookbooks postgresql and database mercurial openssl

Resources

Instance related attributes ```ruby liquid_feedback "OurOrganization" do email_from "lqfb@example.com" area "The Internet" action :create member_ttl '1 year'

# software related attributes
core_version 'v2.1.0'
webmcp_version 'v2.1.0'
frontend_version 'v2.1.2'

end ```

Usage

Via Resource (multi-instance)

Set up one or multiple liquid_feedback resource in your recipe and run it. Your admin invitekey will be written to a template

miminal example script

::Chef::Recipe.send(:include, Opscode::OpenSSL::Password)

node.set_unless['lf']['db_password'] = secure_password
node.set['lf']['db_user'] = "liquid_feedback"

liquid_feedback "org1" do

    email "org1.example.com"
    locale "de_DE.UTF-8"

    db_user node['lf']['db_user']
    db_password node['lf']['db_password']

    action [:create, :start]
end

liquid_feedback "org2" do

    email "org2@example.com"
    locale "en_US.UTF-8"

    db_user node['lf']['db_user']
    db_password node['lf']['db_password']

    action [:create, :start]
end

Via Recipe (single-instance)

Set up node attributes Include recipe.

Your admin invitekey will be stored as node attribute ruby node['lf']['admin_invitecode']

Notes

If you use chef-solo, you must set lf db password and postgresql password in node json directly:

    "lf": {
        "db": {
            "password": "passwordForLQInstanceUser"
        }
    },
    "postgresql": {
        "password": {
            "postgres": "passwordForConncetingToPG"
        }
    }

KNOWN BUGS with using resources: - Lighttpd currently supports only single-instance (web path) - Postgresql supports only one db_user and db_password (pg_hba needs to be setup for all users, circumvent with setting db_user and db_password same on all your resources)

Ideas/Todo

  • Setup Postfix or exim (or email)
  • Send event notifications

  • Set up Unix users for postges access

  • Set up lighttp to run lua scripts as unix users (and find out which access rights they need)

Contact

see metadata.rb

Dependent cookbooks

database >= 0.0.0
openssl >= 0.0.0
mercurial >= 0.0.0
postgresql >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

Collaborator Number Metric
            

1.1.0 failed this metric

Failure: Cookbook has 0 collaborators. A cookbook must have at least 2 collaborators to pass this metric.

Contributing File Metric
            

1.1.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
            

1.1.0 failed this metric

FC017: LWRP does not notify when updated: liquid-feedback/providers/default.rb:24
FC017: LWRP does not notify when updated: liquid-feedback/providers/default.rb:279
FC017: LWRP does not notify when updated: liquid-feedback/providers/default.rb:285
FC043: Prefer new notification syntax: liquid-feedback/providers/default.rb:74
FC043: Prefer new notification syntax: liquid-feedback/providers/default.rb:83
FC043: Prefer new notification syntax: liquid-feedback/providers/default.rb:92
FC043: Prefer new notification syntax: liquid-feedback/providers/default.rb:98
FC043: Prefer new notification syntax: liquid-feedback/providers/default.rb:250
FC043: Prefer new notification syntax: liquid-feedback/providers/default.rb:253
FC043: Prefer new notification syntax: liquid-feedback/providers/default.rb:258
FC043: Prefer new notification syntax: liquid-feedback/providers/default.rb:267
FC043: Prefer new notification syntax: liquid-feedback/providers/default.rb:287
FC059: LWRP provider does not declare use_inline_resources: liquid-feedback/providers/default.rb:1
FC064: Ensure issues_url is set in metadata: liquid-feedback/metadata.rb:1
FC065: Ensure source_url is set in metadata: liquid-feedback/metadata.rb:1
FC066: Ensure chef_version is set in metadata: liquid-feedback/metadata.rb:1
FC067: Ensure at least one platform supported in metadata: liquid-feedback/metadata.rb:1
FC069: Ensure standardized license defined in metadata: liquid-feedback/metadata.rb:1
Run with Foodcritic Version 12.2.1 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

License Metric
            

1.1.0 passed this metric

No Binaries Metric
            

1.1.0 passed this metric

Publish Metric
            

1.1.0 passed this metric

Supported Platforms Metric
            

1.1.0 failed this metric

liquid-feedback should declare what platform(s) it supports.

Testing File Metric
            

1.1.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
            

1.1.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