Skip to content

Leverage community cookbooks #13

Open
@patcon

Description

@patcon

Just noticed that you have a bunch of custom forks. Is it worth submitting the customizations upstream and then pointing the Cheffile to the feature branches with the PR's? And then when they're merged in, just use the simple community syntax? (ie cookbook "statsd"). That way, the Cheffile becomes a little like a TODO list, where you're constantly checking in on it to see when you need to push a PR along, or prod the maintainer to peel a new release, so that you can get back to using the official community version :)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Leverage community cookbooks · Issue #13 · monigusto/vagrant-monigusto