<commit_before># lester

[![Build Status](https://travis-ci.org/mthssdrbrg/lester.svg?branch=master)](https://travis-ci.org/mthssdrbrg/lester)


Lester is a small tool for renewing certificates from Let's Encrypt (or any
ACME-compatible server), for websites set up using S3 and CloudFront.

It uses S3 for storing certificates and expects that the private key for a
registered account is available from S3. Server side encryption is enabled by
default for all objects written by Lester, and it's possible to use KMS as well.

Should be noted that even though only a single domain is passed to `lester`, it
will actually include both the given domain and the `www` subdomain (i.e. `www.<domain>`)
when requesting a new certificate.

# Installation

```shell
gem install lester --pre
```

# Usage

To get started and upload a local private key the following command can be used:

```shell
lester init --domain example.org --storage-bucket example-org-backup --private-key privkey.pem
```

To generate a new certificate, the simplest invocation of `lester` is the
following:

```shell
lester new --domain example.org --site-bucket example-org --storage-bucket example-org-backup --email <EMAIL>
```

To enable server side encryption with KMS, one can specify the `-k / --kms-id`
with eiither a key ID or alias:

```shell
lester new --domain example.org --kms-id alias/letsencrypt --site-bucket example-org --storage-bucket example-org-backup --email <EMAIL>
```

It's also possible to use `renew` rather than `new` if one prefers, the result
will be the same.

See `lester --help` for information about other command-line parameters.

## Copyright

© 2015 <NAME>, see LICENSE.txt (MIT).
<commit_msg>Chop up arguments in code examples in README<commit_after># lester

[![Build Status](https://travis-ci.org/mthssdrbrg/lester.svg?branch=master)](https://travis-ci.org/mthssdrbrg/lester)


Lester is a small tool for renewing certificates from Let's Encrypt (or any
ACME-compatible server), for websites set up using S3 and CloudFront.

It uses S3 for storing certificates and expects that the private key for a
registered account is available from S3. Server side encryption is enabled by
default for all objects written by Lester, and it's possible to use KMS as well.

Should be noted that even though only a single domain is passed to `lester`, it
will actually include both the given domain and the `www` subdomain (i.e. `www.<domain>`)
when requesting a new certificate.

# Installation

```shell
gem install lester --pre
```

# Usage

To get started and upload a local private key the following command can be used:

```shell
lester init --domain example.org \
            --storage-bucket example-org-backup \
            --private-key privkey.pem
```

To generate a new certificate, the simplest invocation of `lester` is the
following:

```shell
lester new --domain example.org \
           --site-bucket example-org \
           --storage-bucket example-org-backup \
           --email <EMAIL>
```

To enable server side encryption with KMS, one can specify the `-k / --kms-id`
with eiither a key ID or alias:

```shell
lester new --domain example.org \
           --site-bucket example-org \
           --storage-bucket example-org-backup \
           --email <EMAIL> \
           --kms-id alias/letsencrypt
```

It's also possible to use `renew` rather than `new` if one prefers, the result
will be the same.

See `lester --help` for information about other command-line parameters.

## Copyright

© 2015 <NAME>, see LICENSE.txt (MIT).

{'fraction_non_alphanumeric': 0.09734762979683972, 'fraction_numerical': 0.0039503386004514675, 'mean_word_length': 3.527458492975734, 'pattern_counts': {'":': 0, '<': 11, '<?xml version=': 0, '>': 11, 'https://': 4, 'lorem ipsum': 0, 'www.': 4, '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': '1388675', 'n_tokens_mistral': 1063, 'n_tokens_neox': 1008, 'n_words': 453}