[ CHEF -1291 ] - Deploy resource seems to re-apply the whole recipe stack, not just the portion we specify
[ CHEF -1293 ] - Knife cookbook delete should default to latest if a version is not specified
[ CHEF -1294 ] - Cookbook uploads that are only metadta changes fail
[ CHEF -1295 ] - cookbook file for preseed files in package resource needs to have its run context set
[ CHEF -1296 ] - Regression: …
See the Deploy resource documentation for more information on how that resource behaves. "repository": "git://github.com/jtimberman/my_app.git", "deploy_to": "/srv/my_app", "revision": { "production": "master" }, "force": { "production": false }, "migrate": { "production": false }, "owner": "nobody", "group": "nogroup",
We also have the ability …
But What If You Need To Deploy To Tomcat?
Once again the corporate overlords make their presence felt :) and you're only allowed to deploy to Tomcat . You can develop everything in JRuby and then roll a WAR file in the end, but why bother when you have Warbler .
Warbler is a gem that will make a WAR file out of your Rails app - pretty convenient. They way it does this is by bundling a copy of JRuby (i.e. you don't need to supply it) and then …
…creating a .gems file at the root of my app with contents similar to what I would put in my config environment.rb to specify that my app requires a gem: faker --version ">=0.3.1"
3) Deploy and Run
So I can deploy my app to heroku with the usual steps git init git add . git commit -m "example app for rake script testing" heroku create git push heroku master heroku rake db:migrate
and run the task remotely: heroku rake admin:fake_people NUM_RECORDS=1
… Webrat:: XML.html document(response) doc.search('script').remove puts Webrat:: XML.inner text(doc)
Gives: Ruby on Rails Overview | Download | Deploy | Code | Screencasts | Documentation | Ecosystem | Community | Blog ......................................... ...
Build and Deploy a Shopify App in 8 minutes
Scaling Rails Screencast - Rack & Metal
[ CHEF -688 ] - Deploy revision strategy does not fetch tags
[ CHEF -693 ] - Nodes should auto-expand
[ CHEF -694 ] - role override and default attributes don't get indexed
[ CHEF -695 ] - No backups kept if backup is set to 1
[ CHEF -697 ] - Cookbook metadata does not convert booleans to "required" or "optional" on ruby 1.8.7 as shown by spec failures
[ CHEF -703 ] …
Daniel DeLeo, for 0.7.10, for the SCM and Deploy resources, as well as some rocking internal refactors
Diego Algorta, for 0.7.12, for fixing a bug where Chef would fail on systems with non-english locales. People of the world, Diego brought you working package resources. :)
Thom May, for 0.7.14, for allowing Chef to manage Yum correctly on CentOS 4.
Thank you all for putting in so much work, and being willing to help each other be successful on a daily basis. I'm …
Piping hot from the kitchen, I'm pleased to announce the release of both Chef 0.7.14 and Ohai 0.3.6. Thom May is awarded the MVP this release for fixing Chef to manage Yum correctly on CentOS4 with some well-appreciated Python skill. Go the snake charmer ;)
The secret sauce of this release however is definitely the Deploy resource, and the incredible amount of work put in by Daniel DeLeo . We received a large amount of feedback on varying deployment …
Deploy / SCM Resources
The chef-deploy project written originally by Ezra Zygmuntowicz to bring Capistrano-strategy deployment to Chef has been ported to Chef proper. The SCM functionality has additionally been extracted into Git and Subversion resources. I'm increasingly excited by the prospects opened by having deployment and scm functionality available as first class citizens in Chef, and hope we can continue …