Right now the shipfile can hold multiple deployers, but most projects only need one deployer, so the data-structure that's needed for multiple ones is quite a bit of overhead.
So, I think I'll make it so a shipfile only has one deployer, and if you want to deploy to a different place, you just specify a different shipfile. This also neatly solves the issue of having separate staging vs production environments (you could have a shipfile named ship.production.json and another named ship.staging.json).
Right now the shipfile can hold multiple deployers, but most projects only need one deployer, so the data-structure that's needed for multiple ones is quite a bit of overhead.
So, I think I'll make it so a shipfile only has one deployer, and if you want to deploy to a different place, you just specify a different shipfile. This also neatly solves the issue of having separate staging vs production environments (you could have a shipfile named
ship.production.json
and another namedship.staging.json
).And the format for a shipfile would be: