Safely run SSH commands on a bunch of machines at the same time (from Ruby).
Inspired by Rush and compatible with Ruby 1.8, 1.9, and JRuby 1.3+!
Rye is a Ruby abstraction for executing shell commands via SSH. By default, Rye errs on the side of caution by running in “safe-mode” which specifies a default whitelist of commands and aggressively escapes all command arguments. For example, file globs and the “rm” command are not available in safe-mode, so you can't do this: rbox.rm('-rf', '/etc/*/').
Rye does not require anything to be installed on the server side (other than an SSH daemon) so it can be run from any machine with Ruby, OpenSSL, and OpenSSH.
You need SSH keys to use Rye. After installing Rye, you can check if you have any by running:
If you get the message “The agent has no identities” you will need to generate a keypair.
The easiest way to work with Rye is to authorize your remote accounts for passwordless logins (otherwise you'll be prompted for a password for every connection).
Enable passwordless logins to remote HOST1 and HOST2:
$ rye authorize HOST1 HOST2
This will copy your public SSH keys to the ~/.ssh/authorized_keys and ~/.ssh/authorized_keys2 files on the remote machine(s).
Enable passwordless logins to the local machine:
$ rye authorize-local
See rye -h for more info.
Shell commands are executed by calling methods on a Rye::Box object.
rbox = Rye::Box.new('hostname') rbox.pwd # => "/home/rye" rbox.uname :a # => "Darwin rye-stage 9.7.0 ..."
Method arguments are sent directly as arguments to the shell command. Single-character Symbols are assumed to be single-character switches. e.g. rbox.uname :a becomes uname -a.
The return value for a command is a modified Array containing the contents of STDOUT split by line. It also gives access to STDERR and the exit code
ret = rbox.uptime # => "11:02 up 16:01, 3 users" ret.stderr # =>  ret.exit_code # => 0 ret.stdout # => "11:02 up 16:01, 3 users" ret.stdout.class # => Array ret.class # => Rye::Rap
You can change directories.
rbox.cd '/tmp' rbox.pwd # => '/tmp' rbox['/etc'].ls # => ['apache', 'init.d', ...] rbox.pwd # => '/etc' rbox.cd # => '/home/rye'
You can specify environment variables.
rbox.setenv('TIPPLE', "Forty Creek") rbox.getenv 'TIPPLE' # => "Forty Creek"
You can add and remove commands to the whitelist.
rbox.add_command :anything, '/path/2/anything' rbox.anything rbox.remove_command :anything rbox.anything # => Rye::CommandNotFound exception
Safe mode can be disabled on one of the following ways.
rbox = Rye::Box.new 'HOST', :safe => false OR rbox.disable_safe_mode
When safe-mode is disabled, you can run any command (regardless of what is defined in the whitelist) with any valid arguments (fileglobs, tildas, etc…).
rbox.kill '-SIGHUP', 1928111 rbox.rm 'path/2/*'
You can also execute any valid shell command.
rbox.execute 'ps aux | grep ruby > /tmp/ruby-process-list'
See the “About Safe Mode” section below for more information.
Shell commands can be executed on multiple machines using a Rye::Set object. Create a “set” of machines.
rbox = Rye::Box.new 'HOST1' rset = Rye::Set.new rset.add_boxes rbox, 'HOST2' # Add boxes as hostnames or objects
Then call methods just like with Rye::Box, except now the return value is an Array of Arrays. The order of return values matches the order the machines were added to the set.
rset.hostname # => [["HOST1"], ["HOST2"]] rset.uname # => [["Darwin"], ["Linux"]]
By default, Rye::Set connects to each machine sequentially in the order they were added to the set. Commands can also be run in parallel.
rset = Rye::Set.new "SETNAME", :parallel => true OR rset.parallel = true
rbox = Rye::Box.new "localhost" rbox.file_upload "README.rdoc", "/tmp" applejack = StringIO.new "Some in-memory content" rbox.file_upload applejack, "/tmp/applejack.txt" rbox.ls "/tmp/" # => [README.rdoc, applejack.txt] rbox.cat "/tmp/applejack.txt" # => "Some in-memory content" filecontent = StringIO.new rbox.file_download "/tmp/applejack.txt", filecontent filecontent.read # => "Some in-memory content"
For local processes, you can bypass Rye::Box and execute commands directly with Rye.shell:
Rye.shell :uptime # => 11:02 up 16:01, 3 users
The first argument must be the command name and the remaining arguments are sent directly as arguments to the command. They're not escaped like with Rye::Box so you can use the asterisk, environment variables, pipes, and redirects etc. Also note that you can specify single character switches as symbols and you can separate arguments or put them into a single String.
Rye.shell :ls, '*' Rye.shell :ls, '-l $HOME' Rye.shell :ls, :l, '$HOME > $TMPDIR/crazy.txt'
The return value is a Rye::Rap object (just like with Rye::Box) so you have access to the exit code and STDERR output:
ret = Rye.shell :ls, 'nofile' ret.exit_code # => 1 ret.stderr # => "sh: nofile: No such file or directory" ret.class # => Rye::Rap
You can't use file globs. This means you can't do this: rbox.ls('*.rb'). ~ also doesn't work!
You can't use environment variables as arguments. This means you can't do this: rbox.echo('$HOME'). However, environment variables are available to the commands you run.
Pipes and operators don't work: |, &&, >, <, ||, ~, etc…
Backticks don't work either: procs=`ps aux`
Why? In safe-mode, all command arguments are escaped which turns all arguments into their literal values.
Using a Ruby interface to execute shell commands is pretty awesome, particularly to run them on several machines simultaneously. That's a lot of power and it's potentially very dangerous. That's why Rye disables this stuff by default. There's probably a way to do it safely but it's not obvious yet (to me). If you have any ideas, I'd love to hear them!
Rye permits only a limited number of system commands to be run. This default whitelist is defined in Rye::Cmd but you can add your own commands as you please (see Example 3).
Via Rubygems, one of:
$ gem install rye $ gem install delano-rye --source http://gems.github.com/
or via download:
Rye doesn't read the ~/.ssh/config file yet
Rye uses OpenSSH's ssh-agent (if it exists). Rye starts it up as a child process and shuts it down using at_exit. If you have code in an at_exit that rely's on Rye, make sure your code runs before Rye's at_exit block is called. For example, Drydock uses at_exit too which is why in bin/rye you can see that Drydock is called explicitly so that Rye's at_exit is executed after Drydock executes a command.
No support for STDIN for commands.
Limited support for interactive shells.
If you find one let me know!
Kalin Harvey (rely.ca)
Mike Cline for giving the okay to use the Rye name.
Justin Case (github.com/justincase/) for fixes
Escape, Copyright (C) 2006,2007 Tanaka Akira <firstname.lastname@example.org>
Rye::Box#instance_exec (for Ruby 1.8) Mauricio Fernandez