Ah, so by making it a multitask, it doesn't necessarily imply we'd be encouraging (or even explicitly allowing via the `lineman deploy` CLI) people to deploy to multiple types of environments at a time. It's simply a conventional away to allow multiple target configurations to exist in a way that grunt can reason with them. Normal `registerTask` is really only appropriate when a given project could only conceivably want to use your task for one thing.

But your example config caught me off guard, because I had no idea that you had in mind that a single "production" deploy might entail firing off to two-or-more different instances. Do people often do that? I'm not an ops expert, but it seems odd to me that pushing to multiple instances in a given environment would be better handled by infrastructure to deal with that replication, no?