octosh 0.0.5 → 0.0.6
Sign up to get free protection for your applications and to get access to all the features.
- data/README.md +48 -1
- data/lib/octosh/cli.rb +2 -8
- data/lib/octosh/version.rb +1 -1
- data/lib/octosh/worker/worker.rb +1 -1
- metadata +2 -2
data/README.md
CHANGED
@@ -3,4 +3,51 @@ Octosh
|
|
3
3
|
|
4
4
|
[![Build Status](https://secure.travis-ci.org/BrianMMcClain/octosh.png)](http://travis-ci.org/BrianMMcClain/octosh)
|
5
5
|
|
6
|
-
For when you feel like you need eight arms to manage your servers
|
6
|
+
For when you feel like you need eight arms to manage your servers
|
7
|
+
|
8
|
+
Octosh (Pronounced "awk-tawsh", short for "Octo-shell") is a tool for interacting with multiple hosts simultaneously either in a scripted manner or an interactive manner.
|
9
|
+
|
10
|
+
|
11
|
+
INSTALL
|
12
|
+
-------
|
13
|
+
|
14
|
+
```gem install octosh```
|
15
|
+
|
16
|
+
|
17
|
+
|
18
|
+
|
19
|
+
|
20
|
+
USAGE
|
21
|
+
-----
|
22
|
+
|
23
|
+
In scripted usage, you may either inline your script or pass a path to a script, which will then be executed on each host that is specified.
|
24
|
+
|
25
|
+
The quickest way to get up and running is using inline scripting. For example…
|
26
|
+
|
27
|
+
```octosh -b "hostname; date" -r 192.168.0.100,192.168.0.101,192.168.0.102```
|
28
|
+
|
29
|
+
A few notes, the assumed user here, since none has been specified, is `root`. If you want to specify a uer per host, the command becomes…
|
30
|
+
|
31
|
+
```octosh -b "hostname; date" -r user1@192.168.0.100,user2@192.168.0.101,user3@192.168.0.102```
|
32
|
+
|
33
|
+
or if you want to specify a universal user for all hosts…
|
34
|
+
|
35
|
+
```octosh -b "hostname; date" -u someuser -r 192.168.0.100,192.168.0.101,192.168.0.102```
|
36
|
+
|
37
|
+
By default, this will prompt for a password for each host. You can also indicate that the password is uniform cross all hosts, in which case the command becomes…
|
38
|
+
|
39
|
+
|
40
|
+
```octosh -b "hostname; date" -u someuser -p -r 192.168.0.100,192.168.0.101,192.168.0.102```
|
41
|
+
|
42
|
+
|
43
|
+
Instead of inline scripting, you can also pass a path to a script to run on each host, like so…
|
44
|
+
|
45
|
+
```octosh -s /path/to/script -u someuser -p -r 192.168.0.100,192.168.0.101,192.168.0.102```
|
46
|
+
|
47
|
+
|
48
|
+
ROADMAP
|
49
|
+
-------
|
50
|
+
|
51
|
+
* Public Key Authentication
|
52
|
+
* Interactive shell with Octosh-specific commands (put, get, read, etc)
|
53
|
+
* Simple DSL for more complex tasks
|
data/lib/octosh/cli.rb
CHANGED
@@ -42,13 +42,9 @@ module Octosh
|
|
42
42
|
options.default_user = user
|
43
43
|
end
|
44
44
|
|
45
|
-
options.password_prompt =
|
46
|
-
opts.on('-p', '--password', 'Prompt for password') do
|
47
|
-
options.password_prompt = true
|
48
|
-
end
|
49
|
-
|
45
|
+
options.password_prompt = true
|
50
46
|
options.uniform_password = false
|
51
|
-
opts.on('-
|
47
|
+
opts.on('-p', '--uniform-password', 'Uniform password') do
|
52
48
|
options.uniform_password = true
|
53
49
|
end
|
54
50
|
|
@@ -58,8 +54,6 @@ module Octosh
|
|
58
54
|
end
|
59
55
|
end.parse!
|
60
56
|
|
61
|
-
puts options.inspect
|
62
|
-
|
63
57
|
if not ARGV.empty? and not options.config
|
64
58
|
puts "Using config file"
|
65
59
|
options.config = ARGV[0]
|
data/lib/octosh/version.rb
CHANGED
data/lib/octosh/worker/worker.rb
CHANGED
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: octosh
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.0.
|
4
|
+
version: 0.0.6
|
5
5
|
prerelease:
|
6
6
|
platform: ruby
|
7
7
|
authors:
|
@@ -9,7 +9,7 @@ authors:
|
|
9
9
|
autorequire:
|
10
10
|
bindir: bin
|
11
11
|
cert_chain: []
|
12
|
-
date: 2012-11-
|
12
|
+
date: 2012-11-18 00:00:00.000000000 Z
|
13
13
|
dependencies: []
|
14
14
|
description: Octosh
|
15
15
|
email:
|