Skip to content

Update README.md with 'Use a production certificate' section #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
askrinnik wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update README.md with 'Use a production certificate' section #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -146,3 +146,16 @@ And the `statics.json` file will be like this:
}
]
```

## Use a production certificate
The image uses the self-signed certificate. It is represented as `server-key.pem` and `server-cert.pem` files in a `data` folder. But there is an ability to replace it with your production certificate.

If you have a PFX file, it should be [converted to `key` and `cert` files with the openssl tool](https://www.bluelabellabs.com/blog/how-to-export-certificates-from-windows-for-use-in-apache-nginx-on-linux/).
Then the files should be bound to a container.

```
docker run -d -p 8443:8000 \
-v $PWD/examples/rewrite/server.key:/data/server-key.pem \
-v $PWD/examples/rewrite/cert.pem:/data/server-cert.pem \
fabriciomendonca/json-server-https
```