Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
A zesty Chef server API wrapper

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.


Spice is a zesty Chef API wrapper. Its primary purpose is to let you easily integrate your apps with a (Chef)[] server easily. Spice provides support for the Chef API


Install this beast via Rubygems:

gem install spice

Of course, You can always grab the source from


Spice has four configuration variables:

Spice.server_url    # default: http://localhost:4000
  Spice.chef_version    # default: 0.10.4. Should be set to the version you have
Spice.client_name   # default: nil. Must be set to a valid admin Chef client
Spice.key_file      # default: nil. Must be set to a file path

To connect to a Chef server at with the "admin" API client, throw this somewhere your app can initialize:

Spice.server_url = ""
Spice.client_name = "admin"
Spice.key_file = "/path/to/keyfile.pem"

Say you had a Chef server v0.10.4 running locally on port 4000 over HTTP, you only need to set your client_name and key_file path:

Spice.client_name = "admin"
Spice.key_file = "/path/to/keyfile.pem"

You can also use the Spice.setup block if you prefer this style:

Spice.setup do |s|
  s.server_url = ""
  s.client_name = "admin"
  s.key_file = "/path/to/keyfile.pem"

Next, we need to create the connection object you'll use to sign your requests and pass them to the Chef server. Previous versions of Spice required you to explicitly call Spice.connect! to set up the connection object. If you use the Spice.setup block, it will call .connect! for you:


If you want to reset your config to their default values:


Deprecation notice

Explicitly setting a host, port, and scheme value has been deprecated in favor of setting a single variable, server_url, which matches the format of Chef's client config parameter, chef_server_url. The old way of defining host, port, and scheme has been removed.


Hat tip

Spice is very heavily inspired by the Twitter gem. Mad props to those folks.

Contributing to spice

  • Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet
  • Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it
  • Fork the project
  • Start a feature/bugfix branch
  • Commit and push until you are happy with your contribution
  • Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
  • Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.


Copyright (c) 2011 Dan Ryan. See LICENSE.txt for further details.

Something went wrong with that request. Please try again.