Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/andrewsosa/compose-tugboat

A tugboat for managing your docker-compose.yml files.
https://github.com/andrewsosa/compose-tugboat

babel commander docker docker-compose es6 eslint inquirer javascript nconf

Last synced: 1 day ago
JSON representation

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

Host: GitHub
URL: https://github.com/andrewsosa/compose-tugboat
Owner: andrewsosa
License: mit
Created: 2017-11-19T05:37:38.000Z (almost 7 years ago)
Default Branch: master
Last Pushed: 2018-07-18T10:26:19.000Z (over 6 years ago)
Last Synced: 2024-10-15T09:32:27.103Z (23 days ago)
Topics: babel, commander, docker, docker-compose, es6, eslint, inquirer, javascript, nconf
Language: JavaScript
Homepage: https://npmjs.com/package/compose-tugboat
Size: 110 KB
Stars: 0
Watchers: 3
Forks: 0
Open Issues: 5
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE

Awesome Lists containing this project

README

# 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 ` 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!

``` sh
$ 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
```bash
# 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] Switch to a different Compose configuration
ls List available Compose configurations
save [options] Save the current configuration as
```

## Built With
- [Commander](https://github.com/tj/commander.js/) – CLI options and subcommands framework.
- [Inquirer](https://github.com/SBoudrias/Inquirer.js/) – Interactive CLI framework.
- [nconf](https://github.com/indexzero/nconf) – Simple Node.js config file management.
- [Babel](https://babeljs.io/) - Next generation JavaScript, today.
- [ESLint](https://eslint.org/) - 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