title: Deploying topologies to different remote clusters?
body: <p>I am developing topologies for storm (storm-project.net). I have 2 remote clusters: staging and production.</p>
  
  <p>I have two storm.yaml files on the client (my laptop that I write code on) that point to the different remote clusters, production.storm.yaml and staging.storm.yaml.</p>
  
  <p>Unfortunately, the only way I know to switch between them is to change a symlink to ~/.storm/storm.yaml before deploying topologies remotely via the "storm jar" command. This is error prone and creates a dependency in the project source tree to something at a rather arbitrary place in the client's file tree.</p>
  
  <p>There has to be a better way. "storm list --config staging.storm.yaml" will give me info about the staging cluster, but I can't find a comparable flag to set the conf file with "storm jar". Or perhaps there is an environment variable like "STORM_HOME" that I can set?</p>