Project

tmuxinator-bosh-console

0.0
Repository is archived
No commit activity in last 3 years
No release in over 3 years
tmuxinator-bosh-consolesuhlig/bosh-tmux-consoleHomepageDocumentationSource CodeBug TrackerWiki
Generates the tmuxinator configuration for all VMs of a BOSH deployment. Each instance (VM) will get its own tmux window with some panes, according to the provided template.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Popularity
Downloads
12,908
Stars
0
Forks
0
Watchers
2
 Releases
Current version
0.3.0
Total releases
7
First release
2017-01-15
Latest release
2017-01-28
 Issues
Open Issues
0
Closed Issues
1
Total Issues
1
Issue Closure Rate
100%
 Pull Requests
Open Pull Requests
0
Closed Pull Requests
32
Merged Pull Requests
42
Pull Request Acceptance Rate
56%
 Development
Primary Language
Ruby
Licenses
MIT
Average date of last 50 commits
2019-07-09
Reverse Dependencies
0

 Dependencies

Development

bundler
>= 0
guard
>= 0
guard-bundler
>= 0
guard-rspec
>= 0
pry
>= 0
rake
>= 0
rb-readline
>= 0
rspec
>= 0
rubocop
>= 0

Runtime

bosh_cli
>= 0
 Project Readme

BOSH tmuxinator console

Build Status

Synopsis

$ tmuxinator-bosh-console cf-warden

will create a new tmuxinator project 'cf-warden'. Each instance (VM) will get its own tmux window with some panes, according to the provided template.

The list of instances is generated by executing bosh instances and therefore lists only the VMs of the current deployment.

Once created, tmuxinator can be used as usual to launch the project:

$ tmuxinator cf-warden

Anything appearing after a single -- argument is appended to bosh ssh, e.g. --gateway-host etc.

Installation

$ gem install tmuxinator-bosh-console

Prerequisites

bosh instances must return zero or more instances.

TODO

  • Think about bosh instances vs. bosh vms. We may or may not be interested in jobs that have no VMs, as produced by bosh vms.
  • repeated --includes and --excludes will make less complex regexes