Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

updating readme

  • Loading branch information...
commit f4792f44bc7bba61d93c1e1313dfb1e9ad8327a6 1 parent f87e24c
@mkocher mkocher authored
Showing with 3 additions and 1 deletion.
  1. +3 −1 README.markdown
View
4 README.markdown
@@ -21,9 +21,11 @@ Soloist (or your preferred method of running chef) usually runs chef-solo as roo
# Does this thing actually work?
Yes. At Pivotal we take testing seriously, and have all projects under CI. Chef recipes for OSX didn't fit into any existing CI solution, so pivotal_workstation [got its own](https://github.com/mkocher/chefci) which builds [most of the recipes](https://github.com/mkocher/chefci/blob/master/build_scripts/build_all.command) every night and on every check in.
-# Pull Requests
+# Forking and Pull Requests
Pull requests are welcomed. Creating a cookbook to keep along side pivotal_workstation allows for easy separation between personal/project metadata/recipes and recipes that are of general utility.
+Chef node attributes allow for easy overriding in your own cookbook. All attributes in pivotal_workstation are set at the default level, so you may simply set node.normal or node.override in your own cookbook. We don't tend to extract node attributes preemptively, but pull requests extracting a node variable so you can override it in your own cookbook are welcomed.
+
# Where's pivotal_server?
It's something we're considering, but it doesn't exist yet. It'll probably show up over at [pivotal_experimental](https://github.com/pivotalexperimental) first.
Please sign in to comment.
Something went wrong with that request. Please try again.