Skip to content
This repository has been archived by the owner on Jul 14, 2021. It is now read-only.

Documented how to run a version of chef-dk under development #1419

Conversation

rmiesen
Copy link
Contributor

@rmiesen rmiesen commented Oct 3, 2017

Signed-off-by: Robert Miesen robert.miesen@gmail.com

Description

I documented a possible mechanism for running the version of chef under active development discovered during the Seattle developer's summit.

Issues Resolved

None.

Check List

Signed-off-by: Robert Miesen <robert.miesen@gmail.com>
@rmiesen rmiesen requested a review from a team October 3, 2017 21:04
Copy link
Contributor

@danielsdeleo danielsdeleo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

left a comment about another way to run the chef command from your checkout, but this is already an improvement.

## Running `chef` Locally

```
bundle exec chef
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For commands that require you to be in a specific working directory (such as running chef install with no arguments), you can set the BUNDLE_GEMFILE env var which will allow you to run your copy of the code from anywhere:

BUNDLE_GEMFILE=~/code/chef-dk/Gemfile bundle exec chef

@lamont-granquist lamont-granquist merged commit d662e43 into chef-boneyard:master Oct 6, 2017
@chef-boneyard chef-boneyard locked and limited conversation to collaborators Feb 14, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants