Files

José Armando García Sancio b2e9527e93 DCOS-422 Implement event emitter

We need this to eventually be able to colorize the output for JSON
TOML, etc. Change all references of print to emitter.publish. We also
removed the subcommand command.

Need to do a `make clean env` after this change.

2015-02-17 06:37:54 +00:00

conf.py

DCOS-226 Generate project documetation

2015-02-01 23:48:12 +00:00

developer_guide.rst

DCOS-226 Generate project documetation

2015-02-01 23:48:12 +00:00

index.rst

DCOS-226 Generate project documetation

2015-02-01 23:48:12 +00:00

modules.rst

DCOS-422 Implement event emitter

2015-02-17 06:37:54 +00:00

README.rst

DCOS-226 Generate project documetation

2015-02-01 23:48:12 +00:00

user_guide.rst

DCOS-226 Generate project documetation

2015-02-01 23:48:12 +00:00

README.rst

DCOS Command Line Interface

The DCOS Command Line Interface (CLI) is a command line utility supporting several commands to provide an user friendly yet powerful way to manage DCOS installations.

Dependencies

git must be installed and on the system path in order to fetch packages from git sources.

Setup

Make sure you meet requirements for installing packages

Clone git repo for the dcos cli:

git clone git@github.com:mesosphere/dcos-cli.git

Change directory to the repo directory:
```
cd dcos-cli
```
Make sure that you have virtualenv installed. If not type:
```
sudo pip install virtualenv
```
Create a virtualenv for the dcos cli project:
```
make env
```

Configure Development Environment

Activate the virtualenv:
```
source env/bin/activate
```
Export DCOS_PATH:
```
export DCOS_PATH=$(pwd)/env
```

Export DCOS_CONFIG:

export DCOS_CONFIG=$(pwd)/tests/data/Dcos.toml

Running POC

Get started by calling DCOS CLI help:
```
dcos --help
```

Running Tests:

Run all DCOS CLI tests (make sure that you are running Zookeeper, Mesos and Marathon):
```
tox
```
List all of the supported test environments:
```
tox --listenvs
```
Run a specific set of tests:
```
tox -e <testenv>
```