poise-application 5.0.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: c93e07d070d363f881e7672ab97cf22c68b978c7
+  data.tar.gz: 1c69c0bbd8a5a8ec56898d6fcef659e4fd30b15f
+SHA512:
+  metadata.gz: 5da9fc90970d626ea3b33b32416bd91f0b123c4d81e495fca950a408afa921e2a5ea7947ae7a3485be59a140694a4d71a9664c513cba2ae492e2f38fcf4ca585
+  data.tar.gz: 5ba5b931737ee9fde0447f8980f3ba772f05e9c58b94ee6033ae0e26d2fe96b19527c4e7b566b923b0bc39c2918d3d3af84a3ece1e34b2b5a070f6983bf0a460

data/.gitignore

@@ -0,0 +1,8 @@
+Gemfile.lock
+test/gemfiles/*.lock
+Berksfile.lock
+.kitchen/
+.kitchen.local.yml
+test/docker/
+coverage/
+pkg/

data/.kitchen.travis.yml

@@ -0,0 +1,9 @@
+---
+driver:
+  name: docker
+  binary: "./docker"
+  socket: tcp://docker.poise.io:443
+  tls_verify: true
+  tls_cacert: test/docker/docker.ca
+  tls_cert: test/docker/docker.pem
+  tls_key: test/docker/docker.key

data/.kitchen.yml

@@ -0,0 +1,8 @@
+---
+#<% require 'poise_boiler' %>
+<%= PoiseBoiler.kitchen(platforms: 'ubuntu-14.04') %>
+
+suites:
+- name: default
+  run_list:
+  - recipe[application_test]

data/.travis.yml

@@ -0,0 +1,23 @@
+sudo: false
+cache: bundler
+language: ruby
+rvm:
+- '2.2'
+addons:
+  apt:
+    packages:
+    - libgecode-dev
+env:
+  global:
+  - USE_SYSTEM_GECODE=true
+  - KITCHEN_LOCAL_YAML=.kitchen.travis.yml
+  - secure: QXR/BZQJDLzdefxrG4WOJYiUCey9l8hNzc5rAAlVqAGWa7Mg5WaPw9adkPD6StZE3k6NN6dnwrX84wL4x5R89RnB2oCU7e1mxfCPR+RRoQcm+BG/7PcLyFz/jO99wZ9R0DYVrT3PwTfTad6ABaQ+II/f+UZQBh4Xf4+rImMCXo8=
+  - secure: IZ0ingfE5sdwCCrBqIxCtiLI8UDoKQBf8eXGsVcanLRI13yo8Tn58XM+NgYE+WOuiQhfdGC2Q8UX8U3df/KVdqftP+JNZ1At7D55i4Pgy3d0ywvBKaxvhPGEs72krqjfT84bsNx2NZwQko2BHPxw9pozxnrEF/h7WR2GZSlJicI=
+bundler_args: "--binstubs=$PWD/bin --jobs 3 --retry 3"
+script:
+- "./bin/rake travis"
+gemfile:
+- test/gemfiles/chef-12.gemfile
+- test/gemfiles/chef-12.2.gemfile
+- test/gemfiles/chef-12.3.gemfile
+- test/gemfiles/master.gemfile

data/Berksfile

@@ -0,0 +1,28 @@
+#
+# Copyright 2015, Noah Kantrowitz
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#
+
+source 'https://supermarket.chef.io/'
+extension 'halite'
+
+# Force the rebuild every time for development.
+cookbook 'poise', gem: 'poise'
+cookbook 'poise-service', gem: 'poise-service'
+cookbook 'application', gem: 'poise-application'
+
+group :test do
+  cookbook 'application_test', path: 'test/cookbooks/application_test'
+  cookbook 'apt'
+end

data/CHANGELOG.md

@@ -0,0 +1,92 @@
+# Poise-Application Changelog
+
+## v5.0.0
+
+* Massive rewrite on top of newer Chef patterns. See the 5.0 README for details.
+
+## v4.1.6
+
+* Support for Chef 12.
+* Add `strict_ssh` option to enable host key checking.
+* Add `keep_releases` option to control number of releases to keep.
+* Allow passing a path to a file for `deploy_key`.
+
+## v4.1.4
+
+* [COOK-3343](https://tickets.opscode.com/browse/COOK-3343) - Can't parse release candidate version number.
+
+## v4.1.2
+
+* [COOK-3343](https://tickets.opscode.com/browse/COOK-3343) - Can't parse release candidate version number.
+
+## v4.1.0
+
+* [COOK-3343] - Can't parse release candidate version number.
+
+## v4.0.0
+
+* Removes compatability with Chef 10.
+* [COOK-3564](https://tickets.opscode.com/browse/COOK-3564) - Replace calls to `Chef::Mixin::RecipeDefinitionDSLCore`.
+
+## v3.0.0
+
+* [COOK-3306]: Multiple Memory Leaks in Application Cookbook.
+
+## v2.0.4
+
+* [COOK-2812]: application cookbook doesn't allow to specify a block as `restart_command`.
+
+## v2.0.2
+
+* [COOK-2537]: Provide proper `respond_to` behavior when using `method_missing`.
+* [COOK-2713]: application resource should Allow sub-resource attributes to propogate up.
+
+### Improvement
+* [COOK-2597]: Allow customization for `shallow_clone` when doing a git deploy.
+
+## v2.0.0
+
+This release is incompatible with previous releases (hence major version change). The recipes used in older versions are deprecated and completely removed. See README.md for further detail.
+
+* [COOK-1673] - `deploy_revision` in the application cookbook gives an argument error.
+* [COOK-1820] - Application cookbook: remove deprecated recipes.
+
+## v1.0.4
+
+* [COOK-1567] - Add git submodules to application cookbook.
+
+## v1.0.2
+
+* [COOK-1312] - string callbacks fail with method not found (really included this time).
+* [COOK-1332] - add `release_path` and `shared_path` methods.
+* [COOK-1333] - add example for running migrations.
+* [COOK-1360] - fix minor typos in README.
+* [COOK-1374] - use runit attributes in unicorn run script.
+
+## v1.0.0
+
+This release introduces the LWRP for application deployment, as well as other improvements. The recipes will be deprecated in August 2012 as indicated by their warning messages and in the README.md.
+
+* [COOK-634] - Implement LWRP for application deployment.
+* [COOK-1116] - use other SCMs than git.
+* [COOK-1252] - add `:force_deploy` that maps to corresponding action of deploy resource.
+* [COOK-1253] - fix rollback error.
+* [COOK-1312] - string callbacks fail with method not found.
+* [COOK-1313] - implicit file based hooks aren't invoked.
+* [COOK-1318] - Create `to_ary` method to resolve issue in resources() lookup on "application[foo]" resources.
+
+## v0.99.14
+
+* [COOK-1065] - use pip in virtualenv during deploy.
+
+## v0.99.12
+
+* [COOK-606] application cookbook deployment recipes should use ipaddress instead of fqdn.
+
+## v0.99.11
+
+* make the `_default` `chef_environment` look like production rails env.
+
+## v0.99.10
+
+* Use Chef 0.10's `node.chef_environment` instead of `node['app_environment']`.

data/Gemfile

@@ -0,0 +1,34 @@
+#
+# Copyright 2009-2015, Opscode, Inc.
+# Copyright 2015, Noah Kantrowitz
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#
+
+source 'https://rubygems.org/'
+
+gemspec path: File.expand_path('..', __FILE__)
+
+def dev_gem(name, path: File.join('..', name), github: nil)
+  path = File.expand_path(File.join('..', path), __FILE__)
+  if File.exist?(path)
+    gem name, path: path
+  elsif github
+    gem name, github: github
+  end
+end
+
+dev_gem 'halite'
+dev_gem 'poise'
+dev_gem 'poise-boiler'
+dev_gem 'poise-service'

data/LICENSE

@@ -0,0 +1,201 @@
+                              Apache License
+                        Version 2.0, January 2004
+                     http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+   "License" shall mean the terms and conditions for use, reproduction,
+   and distribution as defined by Sections 1 through 9 of this document.
+
+   "Licensor" shall mean the copyright owner or entity authorized by
+   the copyright owner that is granting the License.
+
+   "Legal Entity" shall mean the union of the acting entity and all
+   other entities that control, are controlled by, or are under common
+   control with that entity. For the purposes of this definition,
+   "control" means (i) the power, direct or indirect, to cause the
+   direction or management of such entity, whether by contract or
+   otherwise, or (ii) ownership of fifty percent (50%) or more of the
+   outstanding shares, or (iii) beneficial ownership of such entity.
+
+   "You" (or "Your") shall mean an individual or Legal Entity
+   exercising permissions granted by this License.
+
+   "Source" form shall mean the preferred form for making modifications,
+   including but not limited to software source code, documentation
+   source, and configuration files.
+
+   "Object" form shall mean any form resulting from mechanical
+   transformation or translation of a Source form, including but
+   not limited to compiled object code, generated documentation,
+   and conversions to other media types.
+
+   "Work" shall mean the work of authorship, whether in Source or
+   Object form, made available under the License, as indicated by a
+   copyright notice that is included in or attached to the work
+   (an example is provided in the Appendix below).
+
+   "Derivative Works" shall mean any work, whether in Source or Object
+   form, that is based on (or derived from) the Work and for which the
+   editorial revisions, annotations, elaborations, or other modifications
+   represent, as a whole, an original work of authorship. For the purposes
+   of this License, Derivative Works shall not include works that remain
+   separable from, or merely link (or bind by name) to the interfaces of,
+   the Work and Derivative Works thereof.
+
+   "Contribution" shall mean any work of authorship, including
+   the original version of the Work and any modifications or additions
+   to that Work or Derivative Works thereof, that is intentionally
+   submitted to Licensor for inclusion in the Work by the copyright owner
+   or by an individual or Legal Entity authorized to submit on behalf of
+   the copyright owner. For the purposes of this definition, "submitted"
+   means any form of electronic, verbal, or written communication sent
+   to the Licensor or its representatives, including but not limited to
+   communication on electronic mailing lists, source code control systems,
+   and issue tracking systems that are managed by, or on behalf of, the
+   Licensor for the purpose of discussing and improving the Work, but
+   excluding communication that is conspicuously marked or otherwise
+   designated in writing by the copyright owner as "Not a Contribution."
+
+   "Contributor" shall mean Licensor and any individual or Legal Entity
+   on behalf of whom a Contribution has been received by Licensor and
+   subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   copyright license to reproduce, prepare Derivative Works of,
+   publicly display, publicly perform, sublicense, and distribute the
+   Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   (except as stated in this section) patent license to make, have made,
+   use, offer to sell, sell, import, and otherwise transfer the Work,
+   where such license applies only to those patent claims licensable
+   by such Contributor that are necessarily infringed by their
+   Contribution(s) alone or by combination of their Contribution(s)
+   with the Work to which such Contribution(s) was submitted. If You
+   institute patent litigation against any entity (including a
+   cross-claim or counterclaim in a lawsuit) alleging that the Work
+   or a Contribution incorporated within the Work constitutes direct
+   or contributory patent infringement, then any patent licenses
+   granted to You under this License for that Work shall terminate
+   as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+   Work or Derivative Works thereof in any medium, with or without
+   modifications, and in Source or Object form, provided that You
+   meet the following conditions:
+
+   (a) You must give any other recipients of the Work or
+       Derivative Works a copy of this License; and
+
+   (b) You must cause any modified files to carry prominent notices
+       stating that You changed the files; and
+
+   (c) You must retain, in the Source form of any Derivative Works
+       that You distribute, all copyright, patent, trademark, and
+       attribution notices from the Source form of the Work,
+       excluding those notices that do not pertain to any part of
+       the Derivative Works; and
+
+   (d) If the Work includes a "NOTICE" text file as part of its
+       distribution, then any Derivative Works that You distribute must
+       include a readable copy of the attribution notices contained
+       within such NOTICE file, excluding those notices that do not
+       pertain to any part of the Derivative Works, in at least one
+       of the following places: within a NOTICE text file distributed
+       as part of the Derivative Works; within the Source form or
+       documentation, if provided along with the Derivative Works; or,
+       within a display generated by the Derivative Works, if and
+       wherever such third-party notices normally appear. The contents
+       of the NOTICE file are for informational purposes only and
+       do not modify the License. You may add Your own attribution
+       notices within Derivative Works that You distribute, alongside
+       or as an addendum to the NOTICE text from the Work, provided
+       that such additional attribution notices cannot be construed
+       as modifying the License.
+
+   You may add Your own copyright statement to Your modifications and
+   may provide additional or different license terms and conditions
+   for use, reproduction, or distribution of Your modifications, or
+   for any such Derivative Works as a whole, provided Your use,
+   reproduction, and distribution of the Work otherwise complies with
+   the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+   any Contribution intentionally submitted for inclusion in the Work
+   by You to the Licensor shall be under the terms and conditions of
+   this License, without any additional terms or conditions.
+   Notwithstanding the above, nothing herein shall supersede or modify
+   the terms of any separate license agreement you may have executed
+   with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+   names, trademarks, service marks, or product names of the Licensor,
+   except as required for reasonable and customary use in describing the
+   origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+   agreed to in writing, Licensor provides the Work (and each
+   Contributor provides its Contributions) on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+   implied, including, without limitation, any warranties or conditions
+   of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+   PARTICULAR PURPOSE. You are solely responsible for determining the
+   appropriateness of using or redistributing the Work and assume any
+   risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+   whether in tort (including negligence), contract, or otherwise,
+   unless required by applicable law (such as deliberate and grossly
+   negligent acts) or agreed to in writing, shall any Contributor be
+   liable to You for damages, including any direct, indirect, special,
+   incidental, or consequential damages of any character arising as a
+   result of this License or out of the use or inability to use the
+   Work (including but not limited to damages for loss of goodwill,
+   work stoppage, computer failure or malfunction, or any and all
+   other commercial damages or losses), even if such Contributor
+   has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+   the Work or Derivative Works thereof, You may choose to offer,
+   and charge a fee for, acceptance of support, warranty, indemnity,
+   or other liability obligations and/or rights consistent with this
+   License. However, in accepting such obligations, You may act only
+   on Your own behalf and on Your sole responsibility, not on behalf
+   of any other Contributor, and only if You agree to indemnify,
+   defend, and hold each Contributor harmless for any liability
+   incurred by, or claims asserted against, such Contributor by reason
+   of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+   To apply the Apache License to your work, attach the following
+   boilerplate notice, with the fields enclosed by brackets "[]"
+   replaced with your own identifying information. (Don't include
+   the brackets!)  The text should be enclosed in the appropriate
+   comment syntax for the file format. We also recommend that a
+   file or class name and description of purpose be included on the
+   same "printed page" as the copyright notice for easier
+   identification within third-party archives.
+
+Copyright [yyyy] [name of copyright owner]
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

data/README.md

@@ -0,0 +1,239 @@
+# Application cookbook
+
+[![Build Status](https://img.shields.io/travis/poise/application.svg)](https://travis-ci.org/poise/application)
+[![Gem Version](https://img.shields.io/gem/v/poise-application.svg)](https://rubygems.org/gems/poise-application)
+[![Cookbook Version](https://img.shields.io/cookbook/v/application.svg)](https://supermarket.chef.io/cookbooks/application)
+[![Coverage](https://img.shields.io/codeclimate/coverage/github/poise/application.svg)](https://codeclimate.com/github/poise/application)
+[![Gemnasium](https://img.shields.io/gemnasium/poise/application.svg)](https://gemnasium.com/poise/application)
+[![License](https://img.shields.io/badge/license-Apache_2-blue.svg)](https://www.apache.org/licenses/LICENSE-2.0)
+
+A [Chef](https://www.chef.io/) cookbook to deploy applications.
+
+## Getting Started
+
+The application cookbook provides a central framework to deploy applications
+using Chef. Generally this will be web applications using things like Rails,
+Django, or NodeJS, but the framework makes no specific assumptions. The core
+`application` resource provides DSL support and helpers, but the heavy lifting
+is all done in specific plugins detailed below. Each deployment starts with
+an `application` resource:
+
+```ruby
+application '/path/to/deploy' do
+  owner 'root'
+  group 'root'
+
+  # ...
+end
+```
+
+The `application` resource uses the Poise subresource system for plugins. This
+means you configure the steps of the deployment like normal recipe code inside
+the `application` resource, with a few special additions:
+
+```ruby
+application '/path/to/deploy' do
+  # Application resource properties.
+  owner 'root'
+  group 'root'
+
+  # Subresources, like normal recipe code.
+  package 'ruby'
+  git '/path/to/deploy' do
+    repository 'https://github.com/example/myapp.git'
+  end
+  application_rails '/path/to/deploy' do
+    database 'mysql://dbhost/myapp'
+  end
+end
+```
+
+When evaluating the recipe inside the `application` resource, it first checks
+for `application_#{resource}`, as well as looking for an LWRP of the same name
+in any cookbook starting with `application_`. This means that a resource named
+`application_foo` can be used as `foo` inside the `application` resource:
+
+```ruby
+application '/path/to/deploy' do
+  owner 'root'
+  group 'root'
+
+  rails '/path/to/deploy' do
+    database 'mysql://dbhost/myapp'
+  end
+end
+```
+
+Additionally if a resource inside the `application` block doesn't have a name,
+it uses the same name as the application resource itself:
+
+```ruby
+application '/path/to/deploy' do
+  owner 'root'
+  group 'root'
+
+  rails do
+    database 'mysql://dbhost/myapp'
+  end
+end
+```
+
+Other than those two special features, the recipe code inside the `application`
+resource is processed just like any other recipe.
+
+## Available Plugins
+
+* [`application_git`](https://github.com/poise/application_git) – Deploy
+  application code from a git repository.
+* [`application_ruby`](https://github.com/poise/application_ruby) – Manage Ruby
+  deployments, such as Rails or Sinatra applications.
+* [`application_python`](https://github.com/poise/application_python) – Manage
+  Python deployments, such as Django or Flask applications.
+* [`application_javascript`](https://github.com/poise/application_javascript) –
+  Manage server-side JavaScript deployments using Node.js or io.js.
+* `application_java` – *Coming soon!*
+* `application_go` – *Coming soon!*
+* `application_erlang` – *Coming soon!*
+
+## Requirements
+
+Chef 12 or newer is required.
+
+## Resources
+
+### `application`
+
+The `application` resource has top-level configuration properties for each
+deployment and acts as a container for other deployment plugin resources.
+
+```ruby
+application '/opt/test_sinatra' do
+  git 'https://github.com/example/my_sinatra_app.git'
+  bundle_install do
+    deployment true
+  end
+  unicorn do
+    port 9000
+  end
+end
+```
+
+#### Actions
+
+* `:deploy` – Deploy the application. *(default)*
+* `:start` - Run `:start` on all subresources that support it.
+* `:stop` - Run `:stop` on all subresources that support it.
+* `:restart` - Run `:restart` on all subresources that support it.
+* `:reload` - Run `:reload` on all subresources that support it.
+
+#### Properties
+
+* `path` – Path to deploy the application to. *(name attribute)*
+* `environment` – Environment variables for all application deployment steps.
+* `group` – System group to deploy the application as.
+* `owner` – System user to deploy the application as.
+* `action_on_update` – Action to run on the application resource when any
+  subresource is updated. *(default: restart)*
+* `action_on_update_immediately` – Run the `action_on_update` notification with
+  `:immediately`. *(default: false)*
+
+## Examples
+
+Some test recipes are available as examples for common application frameworks:
+
+* [Sinatra](https://github.com/poise/application_ruby/blob/master/test/cookbooks/application_ruby_test/recipes/sinatra.rb)
+* [Rails](https://github.com/poise/application_ruby/blob/master/test/cookbooks/application_ruby_test/recipes/rails.rb)
+* [Flask](https://github.com/poise/application_python/blob/master/test/cookbooks/application_python_test/recipes/flask.rb)
+* [Django](https://github.com/poise/application_python/blob/master/test/cookbooks/application_python_test/recipes/django.rb)
+* [Express](https://github.com/poise/application_javascript/blob/master/test/cookbooks/application_javascript_test/recipes/express.rb)
+
+## Upgrading From 4.x
+
+While the overall design of the revamped application resource is similar to the
+4.x version, some changes will need to be made. The `name` property no longer
+exists, with the name attribute being used as the path to the deployment.
+The `packages` property has been removed as this is more easily handled via
+normal recipe code.
+
+The SCM-related properties like `repository` and `revision` are now handled by
+normal plugins. If you were deploying from a private git repository you will
+likely want to use the `application_git` cookbook, otherwise just use the
+built-in `git` or `svn` resources as per normal.
+
+The properties related to the `deploy` resource like `strategy` and `symlinks`
+have been removed. The `deploy` resource is no longer used so these aren't
+relevant. As a side effect of this, you'll likely want to point the upgraded
+deployment at a new folder or manually clean the `current` and `shared` folders
+from the existing folder. The pseudo-Capistrano layout used by the `deploy`
+resource has few benefits in a config-managed world and introduced a lot of
+complexity and moving pieces that are no longer required.
+
+With the removal of the `deploy` resource, the callback properties and commands
+are no longer used as well. Subresources no longer use the complex
+actions-as-callbacks arrangement as existed before, instead following normal
+Chef recipe flow. Individual subresources may need to be tweaked to work with
+newer versions of the cookbooks they come from, though most have stayed similar
+in overall approach.
+
+## Database Migrations and Chef
+
+Several of the web application deployment plugins include optional support to
+run database migrations from Chef. For "toy" applications where the app and
+database run together on a single machine, this is fine and is a nice time
+saver. For anything more complex I highly recommend not running database
+migrations from Chef. Some initial operations like creating the database and/or
+database user are more reasonable as they tend to be done only once and by their
+nature the application does not yet have users so some level of eventual
+consistency is more acceptable. With migrations on a production application, I
+encourage using Chef and the application cookbooks to handle deploying the code
+and writing configuration files, but use something more specific to run the
+actual migration task. [Fabric](http://www.fabfile.org/),
+[Capistrano](http://capistranorb.com/), and [Rundeck](http://rundeck.org/) are
+all good choices for this orchestration tooling.
+
+Migrations can generally be applied idempotently but they have unique
+constraints (pun definitely intended) that make them tricky in a Chef-like,
+convergence-based system. First and foremost is that many table alterations
+lock the table for updating for at least some period of time. That can mean that
+while staging the new code or configuration data can happen within a window, the
+migration itself needs to be run in careful lockstep with the rest of the
+deployment process (eg. moving things in and out of load balancers). Beyond
+that, while most web frameworks have internal idempotence checks for migrations,
+running the process on two servers at the same time can have unexpected effects.
+
+Overall migrations are best thought of as a procedural step rather than a
+declaratively modeled piece of the system.
+
+## Application Signals and Updates
+
+The `application` resource exposes `start`, `stop`, `restart`, and `reload`
+actions which will dispatch to any subresources attached to the application.
+This allows for generic application-level restart or reload signals that will
+work with any type of deployment.
+
+Additionally the `action_on_update` property is used to set a default
+notification so any subresource that updates will trigger an application
+restart or reload. This can be disabled by setting `action_on_update false` if
+you want to take manual control of service restarts.
+
+## Sponsors
+
+Development sponsored by [Chef Software](https://www.chef.io/), [Symonds & Son](http://symondsandson.com/), and [Orion](https://www.orionlabs.co/).
+
+The Poise test server infrastructure is sponsored by [Rackspace](https://rackspace.com/).
+
+## License
+
+Copyright 2015, Noah Kantrowitz
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.