When you run this on a system, like a throwaway VM or EC2 instance, it will download the cookbooks required for this run list, which you can review what they're going to do after the synchronization step of Chef is complete. With rayburst, the cookbooks will be synchronized into /var/cache/rayburst.
1. Writes out configuration for the chef client.
2. Generates a node on the chef server with the specified "run list" (recipes selected in the rayburst site).
3. Install Ruby and Chef RubyGem
4. Runs Chef with the node that was created on the chef server.
You can download and preview everything before it runs as root on your system.
For example, if you choose the normal stack, you get this run list:
recipe[nginx], recipe[passenger], recipe[postgresql::server], recipe[rails], recipe[ruby]
When you run this on a system, like a throwaway VM or EC2 instance, it will download the cookbooks required for this run list, which you can review what they're going to do after the synchronization step of Chef is complete. With rayburst, the cookbooks will be synchronized into /var/cache/rayburst.