Hi, I've had a go with cuken again. The current gem (not github) fails to setup some of the ssh-steps.
It for example
- complains about the "-b" option at the end of the ssh-forever call
- ssh-forever sets up a lot of keys etc. on the box (you don't want to change your target system in any way)
- is spawns shells
- is changes the .ssh/config files (I would not want that)
I'd love to use cuken for #veewee, but currently I'm still undecided given the ssh-forever dependency.
I see the value of running it just through the command cmd/cuken sweet,
but I think there room for the same implementation through net/ssh .
How would you feel about this? Do I make a new cuken/netssh include and create the same ssh steps?
Or I create a step called And I successfully sshrun or something similar.
thanks for feedback
Hi, I've had a go with cuken again. The current gem (not github) fails to setup some of the ssh-steps.
It for example
I'd love to use cuken for #veewee, but currently I'm still undecided given the ssh-forever dependency.
I see the value of running it just through the command cmd/cuken sweet,
but I think there room for the same implementation through net/ssh .
How would you feel about this? Do I make a new cuken/netssh include and create the same ssh steps?
Or I create a step called And I successfully sshrun or something similar.
thanks for feedback