MPMD deploy

[billmarczak]

Deployer should support different ruby commands & arguments / bud classes & options hashes on different bud instances.

[neilconway]

Yep, this would be very useful. For example, for the fault tolerance stuff I'm working on, I'd like to have different code run at the master (deployer) node than at the children.

Perhaps one way to design this:

• The class that includes XyzDeploy is the "master" deployment class.
• The class that runs on deployed instances is specified via configuration; for example, it could be a Bud option similar to :deploy, or something configured via deploystrap or similar in the master deployment class.
• The client code would need to define some collections to accept data supplied by the deployment framework (e.g., initial_data). This could be done by requiring that the client class must include a Bud-provided module (e.g., DeploymentProtocol).

This wouldn't let you run different code at different deployed instances, but we can add that later easily enough.

[neilconway]

Deply is gone (for now anyway).