Tug

A tugboat for managing your docker-compose.yml files.

Does your project have multiple docker-compose.yml configs? Different configs for dev, prod, or test? Maybe typing docker-compose -f <your_filename> gets tedious.

With tug, you can keep your configurations tucked away and switch between them easily -- it's like version control, but for Docker Compose!

$ tug init
? Where would you like to keep your Compose configs? .docker
? What should we call the active config? master
$ tug checkout -b dev
Switched to dev
$ tug ls
master.yml
dev.yml

Installation

# npm
npm i -g compose-tugboat

# yarn
yarn global add compose-tugboat

Usage

$ tug --help

Usage: tug [options] [command]

Docker Compose configuration management tool

Options:

  -V, --version              output the version number
  -h, --help                 output usage information

Commands:

  init [options]             Initialize Tug
  active [options]           Print the active Compose configuration
  checkout [options] <name>  Switch to a different Compose configuration
  ls                         List available Compose configurations
  save [options] <name>      Save the current configuration as <name>

Built With

• Commander – CLI options and subcommands framework.
• Inquirer – Interactive CLI framework.
• nconf – Simple Node.js config file management.
• Babel - Next generation JavaScript, today.
• ESLint - The pluggable linting utility for JavaScript and JSX.

Contributing

1. Fork it
2. Create your feature branch (git checkout -b my-change)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-change)
5. Create new Pull Request

License

MIT © Andrew Sosa