Skip to content

Commit

Permalink
Update default config naming
Browse files Browse the repository at this point in the history
  • Loading branch information
AdamBark committed Jul 31, 2020
1 parent 193f076 commit 9590ec4
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 6 deletions.
10 changes: 5 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -76,7 +76,7 @@ correctly.
### Binary

```bash
pebble -config ./test/config/pebble-config.json
pebble -config ./test/config/default-config.json
```

Afterwards you can access the Pebble server's ACME directory
Expand Down Expand Up @@ -206,7 +206,7 @@ challenge to observe the state since the CA may send many validation requests.
To test issuance "at full speed" with no artificial sleeps set the environment
variable `PEBBLE_VA_NOSLEEP` to `1`. E.g.

`PEBBLE_VA_NOSLEEP=1 pebble -config ./test/config/pebble-config.json`
`PEBBLE_VA_NOSLEEP=1 pebble -config ./test/config/default-config.json`

The maximal number of seconds to sleep can be configured by defining
`PEBBLE_VA_SLEEPTIME`. It must be set to a positive integer.
Expand Down Expand Up @@ -282,7 +282,7 @@ These endpoints are specific to Pebble and its internal behavior, and are not pa
of the RFC 8555 that defines the ACME protocol.

The management interface is configured by the `managementListenAddress` field in
`pebble-config.json` that defines the address and the port on which the management
`default-config.json` that defines the address and the port on which the management
interface will listen on. Set `managementListenAddress` to an empty string or `null`
to disable it.

Expand Down Expand Up @@ -353,12 +353,12 @@ The endpoint returns the information as a JSON object:
Pebble does not support the OCSP protocol as a responder and so does not set
the OCSP Responder URL in the issued certificates. However, if you setup a
proper OCSP Responder run side by side with Pebble, you may want to set this URL.
This is possible by setting the field `ocspResponderURL` of the `pebble-config.json`
This is possible by setting the field `ocspResponderURL` of the `default-config.json`
consummed by Pebble to a non empty string: in this case, this string will be use
in the appropriate field of all issued certificates.

For instance, to have Pebble issue certificates that instruct a client to check the URL `http://127.0.0.1:4002`
to retrieve the OCSP status of a certificate, run Pebble with a `pebble-config.json` that includes:
to retrieve the OCSP status of a certificate, run Pebble with a `default-config.json` that includes:

```
"ocspResponderURL": "http://127.0.0.1:4002",
Expand Down
2 changes: 1 addition & 1 deletion docker-compose.yml
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@ version: '3'
services:
pebble:
image: letsencrypt/pebble:latest
command: pebble -config /test/config/pebble-config.json -strict -dnsserver 10.30.50.3:8053
command: pebble -config /test/config/default-config.json -strict -dnsserver 10.30.50.3:8053
environment:
# TODO(@cpu): Delete this explicit GODEBUG env var once Pebble is built
# with Go 1.13.x which defaults TLS 1.3 to on
Expand Down

0 comments on commit 9590ec4

Please sign in to comment.