Question 1

How do I set up a tmuxinator project for a web app with multiple services?

Accepted Answer

Define windows for editors, servers, and logs in your YAML file, using arrays for commands and `pre_window` for environment setup. For example, create panes for Rails server and database logs, ensuring proper indentation to avoid YAML errors.

Question 2

Tmuxinator vs manual tmux scripting: which is better for automation?

Accepted Answer

Tmuxinator is better for standardized, reusable session configs with YAML readability, while manual scripts offer more control for complex, dynamic workflows. Choose based on whether you prioritize consistency or customization.

Question 3

Why are my tmuxinator pane commands not executing properly?

Accepted Answer

This can be due to TTY buffer issues on macOS or incorrect YAML indentation. Try putting commands in a script and sourcing it, or check the FAQ for tips on send-keys behavior and pane synchronization settings.

Question 4

Can tmuxinator manage SSH sessions automatically?

Accepted Answer

Yes, by using array commands in panes or windows, such as `- ssh user@host` followed by remote commands, which tmuxinator sends directly via send-keys for seamless integration.

Question 5

How to pass environment variables to a tmuxinator config file?

Accepted Answer

Use ERB templating in the YAML, like `root: <%= ENV["MY_DIR"] %>`, or pass arguments via command-line to access them in `@args` or `@settings` for dynamic paths and settings.

Question 6

What's the difference between local and global tmuxinator projects?

Accepted Answer

Local projects use `.tmuxinator.yml` in the current directory for project-specific configs, ideal for team sharing, while global projects are stored in `~/.tmuxinator` for personal workflow management across different folders.

tmuxinator

What is tmuxinator?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions