Remotely control Google Chrome instances via Hubot.
Torch has three parts: hubot-scripts
, lighter
, and one or more wick
s. They communicate with one other via HTTP.
[ hubot ] (lives on some server)
|
| messages go from irc to internet
|
[ lighter ] (lives on some server, possibly the same one)
/ | \
/ | \ (internet magic http dust)
... | ...
|
[ wick ] (lives on a TV machine, has a 'prefix')
/|\
| (connected to multiple browser windows, indexed prefix1, prefix2, etc)
|
[ browser ]
/|\
tabs..
- Edit
hubot-scripts/torch.coffee
to setLIGHTER_ADDRESS
to the host runninglighter
. - Add it to your hubot scripts directory.
This is the central server which receives commands from hubot and sends them to the hosts running Chrome.
- Install dependencies:
pip install -r lighter/requirements.txt
- Edit
lighter/config.py
to configureprefix_to_channels
, a mapping from TV name prefix (defined in a wick instance's config) to a list of IRC channel names from which users are allowed to control it. - Run
python lighter/lighter.py
.
This is what you'll run on each computer that is connected to a TV/monitor you want to control remotely.
- Install dependencies:
pip install -r wick/requirements.txt
- Edit
wick/config.py
to configurescreen_name_prefix
(prefix to use when naming the browser windows on this computer),port
to run on, andlighter_host
where lighter is running. - Run
python wick/wick.py
.
We wrote this in a day and a half during a hackathon. Some parts are more stable than others. rotate
is known to have some quirks.
http://procatinator.com is a good site to use with the fullscreen on
command.