Deploy

Deployment scheme

Deploy scheme is extremely simple. Resulting tarball resides on some server accessible via https from other nodes running chef.

However such simplicity opens a way to unlimited complications. For example:

• Adding code in chef config to use local cuisine tarball copy if remote url is unavailable
• Use Jenkins or other CI tool to build tarball on each commit and Deploy scheme is extremely simple. Resulting tarball resides on some
• Configure serf or consul to trigger chef run on all boxes when tarball is changed on repo.tanabata.tld
• Reconfigure chef to use local tarball only and push it from your CI
• Anything else =)