tweemux 0.3.0 → 0.4.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- data/README.md +23 -7
- data/lib/tweemux/action/on.rb +1 -0
- data/lib/tweemux/version.rb +1 -1
- data/test/tweemux/action/help_test.rb +1 -1
- metadata +3 -2
data/README.md
CHANGED
|
@@ -11,14 +11,13 @@ Though tmux is an amazing tool, some of the setup for a shared session over the
|
|
|
11
11
|
## Guest Usage
|
|
12
12
|
|
|
13
13
|
gem install tweemux
|
|
14
|
-
tweemux
|
|
15
|
-
# or, specify a port:
|
|
16
|
-
tweemux
|
|
14
|
+
tweemux on somehost.org
|
|
15
|
+
# or, optionally, specify a user and port:
|
|
16
|
+
tweemux on someuser@somehost.org 3322
|
|
17
17
|
|
|
18
|
-
|
|
18
|
+
That should be all it takes for the guest to get started!
|
|
19
19
|
|
|
20
|
-
Now, time to roll up sleeves and get into the details of
|
|
21
|
-
carpet like this for one's pair.
|
|
20
|
+
Now, time to roll up sleeves and get into the details of the other end: hosting.
|
|
22
21
|
|
|
23
22
|
## Host Usage
|
|
24
23
|
|
|
@@ -50,12 +49,29 @@ In this example, sharpsaw.org is a machine that is not behind the firewall:
|
|
|
50
49
|
Then, after your pair can get to your SSHD socket, finally:
|
|
51
50
|
|
|
52
51
|
tweemux host
|
|
53
|
-
# (now they're ready to `tweemux
|
|
52
|
+
# (now they're ready to `tweemux on <yourhost> <your-port>`)
|
|
54
53
|
|
|
55
54
|
## Going Further
|
|
56
55
|
|
|
56
|
+
### GUI sharing
|
|
57
|
+
|
|
57
58
|
It's also nice to share a windowing environment session as well. For example, the "Guest" can host a VNC that you, as the tweemux host, can then connect to. This allows you to "point" at things with the mouse, and to share web browsing, etc.
|
|
58
59
|
|
|
60
|
+
### Tip: ~/.ssh/config
|
|
61
|
+
|
|
62
|
+
tweemux on someuser@somehost.org 3322
|
|
63
|
+
|
|
64
|
+
Then you might consider doing adding a some ~/.ssh/config goodness:
|
|
65
|
+
|
|
66
|
+
Host sh
|
|
67
|
+
Hostname somehost
|
|
68
|
+
User someuser
|
|
69
|
+
port 3322
|
|
70
|
+
|
|
71
|
+
Now you're down to just:
|
|
72
|
+
|
|
73
|
+
tweemux on somehost.org
|
|
74
|
+
|
|
59
75
|
## Details about "Route to your sshd port", above
|
|
60
76
|
|
|
61
77
|
Your options are:
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
class Tweemux::Action::On < Tweemux::Action::At; end
|
data/lib/tweemux/version.rb
CHANGED
|
@@ -10,7 +10,7 @@ class Tweemux::Action
|
|
|
10
10
|
assert_equal stubbed_run.to_yaml, expected_commands.to_yaml
|
|
11
11
|
end
|
|
12
12
|
assert_match /Guest Usage/i, err
|
|
13
|
-
assert_match /tweemux
|
|
13
|
+
assert_match /tweemux on/, err
|
|
14
14
|
assert_match /Host Usage/i, err
|
|
15
15
|
assert_match /tweemux host/, err
|
|
16
16
|
refute_match /Problem/i, err
|
metadata
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: tweemux
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.
|
|
4
|
+
version: 0.4.0
|
|
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: 2013-03-
|
|
12
|
+
date: 2013-03-06 00:00:00.000000000 Z
|
|
13
13
|
dependencies: []
|
|
14
14
|
description: ! 'For Remote Pair Programming: A handy script to create-or-join a world-readable
|
|
15
15
|
tmux session
|
|
@@ -39,6 +39,7 @@ files:
|
|
|
39
39
|
- lib/tweemux/action/help.rb
|
|
40
40
|
- lib/tweemux/action/host.rb
|
|
41
41
|
- lib/tweemux/action/hubkey.rb
|
|
42
|
+
- lib/tweemux/action/on.rb
|
|
42
43
|
- lib/tweemux/action/share.rb
|
|
43
44
|
- lib/tweemux/core_ext.rb
|
|
44
45
|
- lib/tweemux/version.rb
|