Since I occasionally need to pry into our remote staging cluster, I added functionality to connect to remote torquebox instance. The deployment still needs to be pushed manually, but assuming it is already deployed remotely, you can now connect to it via tbconsole.
See below or the individual commits for more information.
Cheers
Changes
lib/torquebox/console/client.rb:
Changed initialize and self.connect to accept a host hash object.
Removed non-static parameters (hosts) from the global constants, renamed to be more descriptive of their functions.
Added build_globals protected method to build STOMP parameters from supplied host and the defaults.
bin/tbconsole:
Added options[:hostname] and options[:port] to the connect definition.
Description
Since I occasionally need to pry into our remote staging cluster, I added functionality to connect to remote torquebox instance. The deployment still needs to be pushed manually, but assuming it is already deployed remotely, you can now connect to it via tbconsole.
See below or the individual commits for more information.
Cheers
Changes
lib/torquebox/console/client.rb:
initialize
andself.connect
to accept a host hash object.build_globals
protected method to build STOMP parameters from supplied host and the defaults.bin/tbconsole:
Added options[:hostname] and options[:port] to the connect definition.