<commit_before>Cloudbreak Deployer helps to deploy a Cloudbreak environment into Docker containers.
For recent changes please check the [CHANGELOG.md](https://github.com/sequenceiq/cloudbreak-deployer/blob/master/CHANGELOG.md).

## Requirements

Currently only **Linux** and **OSX** 64 bit binaries are released for Cloudbreak Deployer. For anything else we will create a special Docker container.
The deployment itself needs only **Docker 1.5.0** or later.

## Installation

To install Cloudbreak Deployer, you just have to unzip the platform specific
single binary to your PATH. The one-liner way is:

```
curl https://raw.githubusercontent.com/sequenceiq/cloudbreak-deployer/master/install | sh && cbd --version
```

## Usage

**cbd** will generate some config files, and will download supporting binaries. It is
advised that you create a dedicated directory for it:

```
mkdir cloudbreak-deployment
cd cloudbreak-deployment
```

### Initialize
First lets initialize your directory by creating a `Profile`

```
cbd init
```


### Pull Docker images

All Cloudbreak components and the backend database is running inside containers.
To download all the needed Docker images, with the correct tag, run the command:

```
cbd pull
```

It will take some time, depending on your network connection, so you can grab a cup of coffee.


### Deploy Cloudbreak

To start all the containers run:

```
cbd start
```
If one of the container is already running, it won’t be started again.

### Watch the logs

```
cbd logs
```

## Default Credentials

If you check the output of `cbd env` you can see the default principal/credential combination:
- user: **<EMAIL>**
- password: **<PASSWORD>**

These values are generated in the `uaa.yml` end section. To change these values, add 2 lines into your Profile:

```
export UAA_DEFAULT_USER_EMAIL=<EMAIL>
export UAA_DEFAULT_USER_PW=<PASSWORD>
```
and than you need to recreate configs:
```
rm *.yml
cbd generate
```

## Debug

If you want to have more detailed output set the `DEBUG` env variable to non-zero:

```
DEBUG=1 cbd some_command
```

You can also use the `doctor` command to diagnose your environment:

```
cbd doctor
```

## Update

The tool is capable to upgrade itself to a newer version.

```
cbd update
```

## Credits

This tool, and the PR driven release, is inspired from [glidergun](https://github.com/gliderlabs/glidergun). Actually it
could be a fork of it. The reason it’s not a fork, because we wanted to have our own binary with all modules
built in, so only a single binary is needed.
<commit_msg>readme: move optional cbd pull after the cbd start command<commit_after>Cloudbreak Deployer helps to deploy a Cloudbreak environment into Docker containers.
For recent changes please check the [CHANGELOG.md](https://github.com/sequenceiq/cloudbreak-deployer/blob/master/CHANGELOG.md).

## Requirements

Currently only **Linux** and **OSX** 64 bit binaries are released for Cloudbreak Deployer. For anything else we will create a special Docker container.
The deployment itself needs only **Docker 1.5.0** or later.

## Installation

To install Cloudbreak Deployer, you just have to unzip the platform specific
single binary to your PATH. The one-liner way is:

```
curl https://raw.githubusercontent.com/sequenceiq/cloudbreak-deployer/master/install | sh && cbd --version
```

## Usage

**cbd** will generate some config files, and will download supporting binaries. It is
advised that you create a dedicated directory for it:

```
mkdir cloudbreak-deployment
cd cloudbreak-deployment
```

### Initialize
First lets initialize your directory by creating a `Profile`

```
cbd init
```
It will create a `Profile` in the correc

### Deploy Cloudbreak

To start all the containers run:

```
cbd start
```
If one of the container is already running, it won’t be started again.


### Pull Docker images

All Cloudbreak components and the backend database is running inside containers.
The **pull command is optional** but you can run it prior to `cbd start`

```
cbd pull
```

It will take some time, depending on your network connection, so you can grab a cup of coffee.


### Watch the logs

```
cbd logs
```


## Default Credentials

If you check the output of `cbd env` you can see the default principal/credential combination:
- user: **<EMAIL>**
- password: **<PASSWORD>**

These values are generated in the `uaa.yml` end section. To change these values, add 2 lines into your Profile:

```
export UAA_DEFAULT_USER_EMAIL=<EMAIL>
export UAA_DEFAULT_USER_PW=<PASSWORD>
```
and than you need to recreate configs:
```
rm *.yml
cbd generate
```

## Debug

If you want to have more detailed output set the `DEBUG` env variable to non-zero:

```
DEBUG=1 cbd some_command
```

You can also use the `doctor` command to diagnose your environment:

```
cbd doctor
```

## Update

The tool is capable to upgrade itself to a newer version.

```
cbd update
```

## Credits

This tool, and the PR driven release, is inspired from [glidergun](https://github.com/gliderlabs/glidergun). Actually it
could be a fork of it. The reason it’s not a fork, because we wanted to have our own binary with all modules
built in, so only a single binary is needed.

{'fraction_non_alphanumeric': 0.09092660373723753, 'fraction_numerical': 0.0026969755345790792, 'mean_word_length': 4.471022128556375, 'pattern_counts': {'":': 0, '<': 11, '<?xml version=': 0, '>': 11, 'https://': 6, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 3, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2154812', 'n_tokens_mistral': 1560, 'n_tokens_neox': 1465, 'n_words': 697}