Skip to content
Commits on Apr 13, 2011
  1. Tag 0.5.1

  2. Added cookbooks/README so that unit tests would fail without Peter's …

    Changed "role.has_key" to "key in role"
  3. Don't error if a role doesn't have a description

    Peter Harkins committed
  4. Don't error if a role doesn't define default_attributes or override_a…

    Peter Harkins committed
  5. Path fix

    Peter Harkins committed
  6. Ignore files in cookbooks/

    Peter Harkins committed
  7. Add missing parens

    Peter Harkins committed
Commits on Mar 31, 2011
Commits on Mar 30, 2011
  1. Add first unit tests

    Improve printing of list_* functions
  2. fixed documentation

    Tobias von Klipstein committed with
  3. corrected spelling of maverick

    Tobias von Klipstein committed with
  4. Fix dependency string

  5. Bump up dependency to fabric>=1.0.1

    Remove pty=True argument from all calls, as it is the default in fabric 1.0
  6. Upload cookbooks in a single tar again. Speeds up upload a lot.

    Node synching doesn't configure chef-solo everytime, gaining another speed up
  7. changed deploy_solo to _configure_chef_solo

    Better error reporting when chef-solo is not installed on the node
    Added some colors
  8. Change chef-solo files path to /var/chef-solo

    Change string interpolation formatting to the Python 3 style format()
  9. Merge branch 'next' of git://

Commits on Mar 22, 2011
  1. Add list_roles_detailed, simplify list_roles, adding tab aligned role…

    … description to both and to list_recipes
Commits on Mar 10, 2011
  1. Tag version 0.4.2

Commits on Mar 8, 2011
  1. Make fabric depend on version 0.9.3 to avoid getting 1.0, which is no…

    …t fully backwards compatible
  2. Improve README and docstrings

  3. @igal

    Fix security of files by enforcing root ownership and restrictive modes.

    igal committed
    Previously files were uploaded to a non-root user's homedir with default
    permissions, usually wide-open, and copied into place still owned as that
    user. This was bad because these files contain sensitive information that
    shouldn't be readable to anyone other than root, and certainly not
    writeable by anyone else.
  4. @igal
  5. @igal

    Fix use of insecure work path on nodes.

    igal committed
    Previously, the program blindly deployed to "/tmp/chef-solo" -- which is
    insecure and bad because an attacker could create this directory and add
    files to it that they'd like to have run as root.
    The new approach creates a "/var/littlechef" directory, which only root
    can create and use.
  6. @igal

    Add "site-cookbooks", fix "append" calls, and always deploy chef-solo.

    igal committed
    If a "site-cookbooks" directory is found, its contents will selectively
    override those in "cookbooks".
    Fixed "append" operations, they were failing because they didn't use sudo
    and had the arguments for filename and content backwards.
    A new "deploy_solo" task ensures that the node has a fresh "solo.rb" and
    directory structure. Previously this was created only during "deploy_chef",
    which was a problem because "solo.rb" would be out of date and there would
    be no tidy way to regenerate it. Now this task is run as part of the
    "configure" and "deploy_chef" tasks to ensure there's always a good setup.
Commits on Mar 7, 2011
  1. @igal

    Add ability for "cook" to display version.

    igal committed
    This new code parses options so that they can be handled by littlechef
    and not passed on to fabric.
  2. @igal
  3. @igal
  4. @igal

    Improve "cook" to try loading littlechef module with "import" first.

    igal committed
    This makes it possible to run "cook" from a source code checkout without
    installing the package first, which simplifies installation and development.
    All previous trickery to load the module is retained and will be used as
    a fallback.
Commits on Jan 26, 2011
Commits on Jan 19, 2011
  1. Update README and tag 0.4.1

Commits on Jan 18, 2011
  1. Merge branch 'pythonize-new_deployment' of…

    …tlechef into sit-pythonize-new_deployment
Something went wrong with that request. Please try again.