README.md in bib-vagrant-0.1.1 vs README.md in bib-vagrant-0.1.2

@@ -41,10 +41,27 @@
 #Additional JSON to be merged in the Chef JSON
 additional_json: ! '{}'
 
 #Show Virtualbox GUI
 gui: false
+
+# Token to use with composer
+composer_github_token: <github token>
+
+# npm proxy in the form of "http://npm-proxy.tld/"
+npm_registry: <npm registry or proxy url>
+
+# your npm user email address in the form of [e-mail]
+npm_username: <github or npm username>
+
+# your npm or user email address in the form of [e-mail]
+npm_usermail: <npm or github users email address>
+
+# Authentication Token to use with npm
+npm_userpass: <npm or github authentication token>
+
+
 ```
 
 Additional parameters can be added to the file and used in the Vagrantfile - but you then have to make sure to use sensible fallback defaults in your Vagrantfile, since not every developer might have this setting in the .yml.
 
 
@@ -73,11 +90,13 @@
     web_config.vm.provision :chef_solo do |chef|
       chef.cookbooks_path = vagrantconfig["cookbook_path"]
       chef.add_recipe "something::here"
       chef.log_level = vagrantconfig["chef_log_level"]
     end
-
+    
+    web_config.vm.provision "bib_configure_npm" 
+    
   end
 ```
 
 The configuration is located in `~/.config/easybib/vagrantdefault.yml`:
 
@@ -86,9 +105,14 @@
 nfs: false
 cookbook_path: ~/Documents/workspaces/easybib-cookbooks
 chef_log_level: debug
 additional_json: ! '{}'
 gui: true
+composer_github_token: <github token>
+npm_registry: <npm registry or proxy url>
+npm_username: <github or npm username>
+npm_usermail: <npm or github users email address>
+npm_userpass: <npm or github authentication token>
 ```
 
 ## Contributing
 
 See [Contributing](CONTRIBUTING.md)