Skip to content

docker changelog #391

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

Merged
MadelineMurray merged 4 commits into from
Feb 13, 2020
Merged

docker changelog #391

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
8ebb652
docker changelog
RatanRSur Feb 12, 2020
d86a6e2
address comments
RatanRSur Feb 12, 2020
ffa503c
Merge branch 'master' into docker-changelog
MadelineMurray Feb 13, 2020
1e5ff52
Merge branch 'master' into docker-changelog
MadelineMurray Feb 13, 2020
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
4 changes: 4 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,10 @@

This can be enabled using the `--rpc-http-api TRACE` CLI flag. There are some philosophical differences between Besu and other implementations that are outlined in [trace_rpc_apis](docs/trace_rpc_apis.md).

- Ability to automatically detect Docker NAT settings from inside the conainter.
Copy link
Copy Markdown
Contributor

@MadelineMurray MadelineMurray Feb 12, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this probably needs to go below the following paragraph -> the following paragraph describes the bullet point above this one.

Is it enabled using a CLI option? It'd be good to give the changelog reader some idea of how to enable this.


The default NAT method (AUTO) can detect this so no user intervention is required to enable this.

- Added [Multi-tenancy](https://besu.hyperledger.org/en/latest/Concepts/Privacy/Multi-Tenancy/) support which allows multiple participants to use the same Besu node for private transactions.

- Added TLS support for communication with privacy enclave
Expand Down