joeduffy 361eb62e7b Move coco env deploy to the top-level, coco deploy ... Deployments are central to the entire system; although technically a deployment is indeed associated with an environment, the deployment is the focus, not the environment, so it makes sense to put the deployment command at the top-level. Before, you'd say: $ coco env deploy production And now, you will say: $ coco deploy production		2017-03-10 13:17:55 -08:00
..
coconut.go	Move coco env deploy to the top-level, coco deploy	2017-03-10 13:17:55 -08:00
deploy.go	Move coco env deploy to the top-level, coco deploy	2017-03-10 13:17:55 -08:00
env.go	Move coco env deploy to the top-level, coco deploy	2017-03-10 13:17:55 -08:00
env_config.go	Properly reap child processes	2017-03-07 13:47:42 +00:00
env_destroy.go	Properly reap child processes	2017-03-07 13:47:42 +00:00
env_init.go	Properly reap child processes	2017-03-07 13:47:42 +00:00
env_ls.go	Properly reap child processes	2017-03-07 13:47:42 +00:00
env_rm.go	Properly reap child processes	2017-03-07 13:47:42 +00:00
pack.go	Rename the coco nut command to coco pack	2017-03-09 15:43:28 +00:00
pack_eval.go	Add the ability to specify and env config during eval	2017-03-09 15:52:50 +00:00
pack_get.go	Rename the coco nut command to coco pack	2017-03-09 15:43:28 +00:00
pack_info.go	Rename the coco nut command to coco pack	2017-03-09 15:43:28 +00:00
pack_verify.go	Rename the coco nut command to coco pack	2017-03-09 15:43:28 +00:00
version.go	Properly reap child processes	2017-03-07 13:47:42 +00:00