<commit_before># docker-gen for Docker Cloud

This is an enhancment to the [docker-gen](https://github.com/jwilder/docker-gen) image that adds support
for [Docker Cloud](https://cloud.docker.com).

This image is used in context of [this](https://blog.switchbit.io/developing-a-ghost-theme-with-gulp-part-5/) 
post on using [JrCs/docker-letsencrypt-nginx-proxy-companion](https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion)
to generate Let's Encrypt certificates for a Ghost specific stack. 

# The problem

The usual way of using `docker-gen` in conjunction with `docker-letsencrypt-nginx-proxy-companion` using the separate
container method, is as follows (as per the [docs](https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion#separate-containers-recommended-method)):

```
$ docker run -d \
    --name nginx-gen \
    --volumes-from nginx \
    -v /path/to/nginx.tmpl:/etc/docker-gen/templates/nginx.tmpl:ro \
    -v /var/run/docker.sock:/tmp/docker.sock:ro \
    jwilder/docker-gen \
    -notify-sighup nginx -watch -only-exposed -wait 5s:30s /etc/docker-gen/templates/nginx.tmpl /etc/nginx/conf.d/default.conf
```

however, within a Docker Cloud based environment we cannot use `-notify-sighup nginx` due to the fact that
the container names (on the actual nodes) do not match their [Service](https://docs.docker.com/docker-cloud/apps/stacks/) names.
The result is that the `nginx` container (Service) never get's reloaded to take advantage of the generated Nginx configuration.

# The solution<commit_msg>spelling: enhancement<commit_after># docker-gen for Docker Cloud

This is an enhancement to the [docker-gen](https://github.com/jwilder/docker-gen) image that adds support
for [Docker Cloud](https://cloud.docker.com).

This image is used in context of [this](https://blog.switchbit.io/developing-a-ghost-theme-with-gulp-part-5/) 
post on using [JrCs/docker-letsencrypt-nginx-proxy-companion](https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion)
to generate Let's Encrypt certificates for a Ghost specific stack. 

# The problem

The usual way of using `docker-gen` in conjunction with `docker-letsencrypt-nginx-proxy-companion` using the separate
container method, is as follows (as per the [docs](https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion#separate-containers-recommended-method)):

```
$ docker run -d \
    --name nginx-gen \
    --volumes-from nginx \
    -v /path/to/nginx.tmpl:/etc/docker-gen/templates/nginx.tmpl:ro \
    -v /var/run/docker.sock:/tmp/docker.sock:ro \
    jwilder/docker-gen \
    -notify-sighup nginx -watch -only-exposed -wait 5s:30s /etc/docker-gen/templates/nginx.tmpl /etc/nginx/conf.d/default.conf
```

however, within a Docker Cloud based environment we cannot use `-notify-sighup nginx` due to the fact that
the container names (on the actual nodes) do not match their [Service](https://docs.docker.com/docker-cloud/apps/stacks/) names.
The result is that the `nginx` container (Service) never get's reloaded to take advantage of the generated Nginx configuration.

# The solution
{'fraction_non_alphanumeric': 0.12422964644826467, 'fraction_numerical': 0.0025948751216347712, 'mean_word_length': 4.089108910891089, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 12, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6807849', 'n_tokens_mistral': 1082, 'n_tokens_neox': 987, 'n_words': 274}