Implement knife-solo to make the project deployable?

[patcon]

Ok, firstly: THIS IS FREAKING AWESOME.

https://github.com/matschaffer/knife-solo
knife-solo might be interesting to help people deploy to remote servers. Not sure if this is in line with the project goals, or if you'd rather people just test-drive it with vagrant, and then steal pieces for integration into their own infra.
cc: @matschaffer

I'm hitting a similar situation... Almost feeling like I need a way to help distribute packages of cookbooks and roles that can be embedded in other cookbook repos or projects... When people cherry-pick cookbooks and config, they detach themselves from upstream improvements that might happen, and that kinda sucks.

Also, you might want to check out @heavywater's echelon project, if you haven't already:
https://github.com/heavywater/echelon

[matschaffer]

Given the cookbook layout you could probably do it fairly easily. I also have a half baked knife-solo provisioner that might help if someone wanted to try it out https://github.com/matschaffer/knife-solo/blob/rspec-vagrant/spec/integration/support/knife_solo_provisioner.rb

[matschaffer]

and yes this is fricking awesome. Can't wait to try it tomorrow. 🍻