A site should be able to have multiple, named deploy configurations. This would allow a site to have a "preview" or "staging" server along with a "production" server, each with different configurations. This can help with approval workflows.
To configure named deploys, the configuration file should accept a hash of deploys in addition to a single deploy:
With this configuration, you could run statocles deploy preview to deploy to the preview server, or statocles deploy prod to deploy to production. A special deploy named "default" would be used when one simply does statocles deploy.
When only one deploy exists, that deploy should be the "default" deploy.
A site should be able to have multiple, named deploy configurations. This would allow a site to have a "preview" or "staging" server along with a "production" server, each with different configurations. This can help with approval workflows.
To configure named deploys, the configuration file should accept a hash of deploys in addition to a single deploy:
With this configuration, you could run
statocles deploy preview
to deploy to the preview server, orstatocles deploy prod
to deploy to production. A special deploy named "default" would be used when one simply doesstatocles deploy
.When only one deploy exists, that deploy should be the "default" deploy.