Skip to content
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.

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

Fixes typo in docs #571

Merged
merged 1 commit into from Mar 5, 2019
Merged
Changes from all commits
Commits
File filter...
Filter file types
Jump to…
Jump to file or symbol
Failed to load files and symbols.
+2 −2
Diff settings

Always

Just for now

@@ -255,7 +255,7 @@ run(new ServiceSpec)

[mu] derives a client automatically based on the protocol. This is especially useful because you can distribute it depending on the protocol/service definitions. If you change something in your protocol definition, you will get a new client for free without having to write anything.

You will need to add either `mu-rpc-client-netty` or `mu-rpc-client-okhttp` to your build.
You will need to add either `mu-rpc-netty` or `mu-rpc-okhttp` to your build.

### Client Runtime

@@ -22,7 +22,7 @@ On the server and client side, we will need two files to configure the `SslConte

## Usage

The first step to secure our [mu] services is to add the library dependencies `mu-rpc-netty-ssl` and `mu-rpc-client-netty` in our build.
The first step to secure our [mu] services is to add the library dependencies `mu-rpc-netty-ssl` and `mu-rpc-netty` in our build.

For the second step, we have to move both server/client certificates and private keys to the `resources` folder.

ProTip! Use n and p to navigate between commits in a pull request.
You can’t perform that action at this time.