No commit activity in last 3 years
No release in over 3 years
Create and manage complex tmux and iTerm sessions easily.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

~> 1.0.0
~> 1.5.1
>= 0
~> 2.1.0
 Project Readme

Tmuxinator

Create and manage tmux and iTerm2 sessions easily. Fork of (Tmuxinator).

Note: while Terminitor has iTerm support, it relies on sending keypresses to iTerm. This project uses AppleScript and can, therefore, connect with iTerm on a deeper level. I also like tmuxinator's config format and it's nice to have one config that can be used on a Mac or a non-GUI'd machine.

Installation

$ gem install dkastner-tmuxinator

Note: This fork plays well with existing tmuxinator installs.

Then follow the instructions. You just have to drop a line in your ~/.bashrc file, similar to RVM if you've used that before:

[[ -s $HOME/.tmuxinator/scripts/tmuxinator ]] && source $HOME/.tmuxinator/scripts/tmuxinator

Editor and Shell

tmuxinator uses your shell's default editor for opening files. If you're not sure what that is type:

$ echo $EDITOR

For me that produces "vim" If you want to change your default editor simple put a line in ~/.bash_profile that changes it. Mine looks like this:

export EDITOR='vim'

It also uses $SHELL variable. which is always set by your shell.

Usage

Create a project

$ tmuxinator new project_name

Create or edit your projects with this command, for editing you can also use tmuxinator open project_name. new aliased to o,open and n. Your default editor ($EDITOR) is used to open the file. If this is a new project you will see this default config:

# ~/.tmuxinator/project_name.yml
# you can make as many tabs as you wish...

project_name: Tmuxinator
project_root: ~/code/rails_project
rvm: 1.9.2@rails_project
pre: sudo /etc/rc.d/mysqld start
tabs:
  - editor:
      layout: main-vertical
      panes:
        - vim
        - #empty, will just run plain bash
        - top
  - shell: git pull
  - database: rails db
  - server: rails s
  - logs: tail -f logs/development.log
  - console: rails c
  - capistrano:
  - server: ssh me@myhost

If a tab contains multiple commands, they will be 'joined' together with '&&'. If you want to have your own default config, place it into $HOME/.tmuxinator/default.yml

The pre command allows you to run anything before starting the tmux/iTerm session. Could be handy to make sure you database daemons are running. Multiple commands can be specified, just like for tabs.

Panes Support

you can define your own panes inside a window likes this:

- window_with_panes
    layout: main-vertical
    panes:
      - vim
      - #empty, will just run plain bash
      - top

Starting a project

$ start_project_name

This will fire up tmux with all the tabs you configured.

$ iterm_project_name

This will fire up iTerm with all the tabs you configured.

Limitations

After you create a project, you will have to open a new shell window. This is because tmuxinator adds an alias to bash (or any other shell you use, like zsh) to open tmux with the project config. You can reload your shell rc file instead of openning a new window like this, for instance in bash you could do this:

$ source ~/.bashrc

Other Commands

$ tmuxinator copy existing_project new_project

Copy an existing project. aliased to c

$ tmuxinator update_scripts

Re-create the tmux and iTerm scripts and aliases from the configs. Use this only if you edit your project configs outside of tmuxinator, i.e. not using "tmuxinator open xxx".

$ tmuxinator list

List all the projects you have configured. aliased to l

$ tmuxinator delete project_name

Remove a project

$ tmuxinator implode

Remove all tmuxinator configs, aliases and scripts. aliased to i

$ tmuxinator doctor

Examines your environment and identifies problems with your configuration

$ tmuxinator version

shows tmuxinator's version. aliased to v

$ tmuxinator help

shows tmuxinator's help. aliased to h

Contributing to tmuxinator

  • Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet
  • Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it
  • Fork the project
  • Start a feature/bugfix branch
  • Commit and push until you are happy with your contribution
  • Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
  • Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.

Copyright

Copyright (c) 2010 Derek Kastner. See LICENSE.txt for further details.