Why? One would imagine that we could compile our Python, Node, or Java projects into a ZIP file and upload them to AWSm Lambda without issue. Unfortunantly AWS Lambda’s execution environment stipulates everything should be compiled in the runtime environment. Makes sense - compile under the same criteria you’re running under.
When I did this manually my workflow was:
Create an Amazon Linux instance Install git Commit code SSH into EC2 instance and do a git pull master Run a shell script to package my Python code and deploy it to AWS Lambda Pretty manual process - and I totally forgot to turn off my ‘build’ EC2 instance - accruing some charges for idling.
Getting Started To begin, install Chef’s omnibus installer: Chef DK
Chef uses the chef tool for creating cookbooks, downloading cookbooks, and many other things.
chef generate repo chef-repo
This creates a chef-repo for connecting to Chef Server.
While this is great for getting started with Chef, creating cookbooks and keeping them in version control gets weird, since this is a single repo.
Cookbooks Chef Cookbooks are composed of recipes written in Ruby plus a Chef Ruby sugar for automating installing an application like Redis, Postgres, Solr, etc.