https://github.com/worr/wsh

A tool that allows you to run commands on multiple hosts
https://github.com/worr/wsh

Last synced: 13 days ago
JSON representation

A tool that allows you to run commands on multiple hosts

• Host: GitHub
• URL: https://github.com/worr/wsh
• Owner: worr
• License: mit
• Created: 2013-01-09T05:32:55.000Z (almost 12 years ago)
• Default Branch: master
• Last Pushed: 2019-12-26T00:00:46.000Z (almost 5 years ago)
• Last Synced: 2024-08-01T22:52:33.026Z (3 months ago)
• Language: C
• Homepage: http://wsh.worrbase.com/
• Size: 977 KB
• Stars: 28
• Watchers: 6
• Forks: 8
• Open Issues: 9
• Metadata Files:
  • Readme: README.md
  • Contributing: CONTRIBUTING.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# wsh

[![Travis](https://img.shields.io/travis/worr/wsh.svg)](https://travis-ci.org/worr/wsh)

[![Coveralls](https://img.shields.io/coveralls/worr/wsh.svg)](https://coveralls.io/github/worr/wsh)

[![Coverity Scan](https://img.shields.io/coverity/scan/10090.svg)](https://scan.coverity.com/projects/worr-wsh)

[![Gitter](https://img.shields.io/gitter/room/worr/wsh.svg)](https://gitter.im/worr/wsh)

wsh is a shell-like program made for devops and sysadmins that need to 

administer several machines at once. With `wsh`, you can ssh into multiple 

machines and run one-off commands very simply

## What wsh isn't

* configuration management 

* a shell 

* an `ssh` replacement

## Dependencies

* `glib2` >= 2.32

* `libssh` >= 0.6.0 (**NOT** `libssh2`) 

* `protobuf-c`

* `sudo`

### Build deps

* `cmake`

* c compiler (`gcc`/`clang`) 

* `make`/`ninja`

* `doxygen` if you want API docs

## Architecture

`wshd` is a program that resides on remote hosts. `wshc` ssh's into

them, honoring your ssh config and exec's `wshd`. Over the secure ssh

pipe, `wshc` issues instructions to `wshd`, and `wshd` executes them on

the remote host. If privileges need to be raised, `wshc` will prompt

you for creds prior to ssh'ing, and submit them once the ssh

connection has been established.

## Advantages

* configuration-less

wsh honors your existing `ssh` and `sudo` configuration files, leaving

all of the work of authorization and authentication to `ssh` and `sudo`

* sudo-ready

Unlike `dsh`, wsh has `sudo` support built in, so that you don't need

to use some kind of hack to get your `sudo` creds over the network.

* logging

wsh logs everything to syslog

# BUILDING

```bash

$ mkdir build

$ cd build

$ cmake ..

$ make

$ sudo make install

```

# How does this compare to ansible and fabric?

I happen to have 1600 hosts lying around so...

```

wshc -f hosts -t 100 -- uname -a  18.88s user 2.02s system 92% cpu 22.630 total

ansible all -i ./hosts -f 30 -a "uname -a"  702.94s user 8.69s system 128% cpu 9:11.77 total

fab -H $(paste -s hosts -d,) -D -P -- uname -a  176.96s user 90.55s system 332% cpu 1:20.55 total

[ worr on worr-ld1 ] ( ~ ) % wc -l hosts

1611 hosts

```

# Where can I get help?

File an issue, or ask me on gitter!