nemunaire/nemunai.re
1
0
Fork 0
Code Issues Pull requests 1 Releases Activity

Fix spelling

Browse source
This commit is contained in:
nemunaire 2023-10-27 17:22:42 +02:00
commit ac3ecece99
2 changed files with 9 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

8
content/en/post/woodpecker-ci-mixing-http-grpc-on-one-domain-nginx/index.md
View file

@ -68,7 +68,7 @@ As such, many reverse-proxies are capable of transmitting GRPC requests.
This is the case of [Caddy](https://woodpecker-ci.org/docs/administration/proxy#caddy), a brief example of which is given, [Traefik](https://woodpecker-ci.org/docs/administration/proxy#traefik).
But `nginx` also [supports the transmission of GRPC requests](https://www.nginx.com/blog/nginx-1-13-10-grpc/).
When a GRPC request is received by the reverse-proxy, it sees an HTTP/2 request similar to :
When a GRPC request is received by the reverse-proxy, it sees an HTTP/2 request similar to:
```
POST /pkg.Service/Function HTTP/2.0
@ -88,7 +88,7 @@ Each *Service* is declared within a package (*pkg*), then *Functions* complete t
All calls are `POSTs`.
So we need to extract the various HTTP routes used by each protobuf service.
Let's take a look at the following file for Wookpecker :
Let's take a look at the following file for Woodpecker:
<https://github.com/woodpecker-ci/woodpecker/blob/main/pipeline/rpc/proto/woodpecker.proto>
@ -135,7 +135,7 @@ For example:
## `nginx` configuration
So here's what our `nginx` configuration might look like, using a single :
So here's what our `nginx` configuration might look like, using a single domain:
```
server {
@ -181,7 +181,7 @@ This causes a large number of reconnections for the Woodpecker agent, visible in
{"level":"error","error":"rpc error: code = Unavailable desc = unexpected HTTP status code received from server: 504 (Gateway Timeout); transport: received unexpected content-type \"text/html\"","time":"2023-10-27T11:28:51Z","message":"grpc error: wait(): code: Unavailable: rpc error: code = Unavailable desc = unexpected HTTP status code received from server: 504 (Gateway Timeout); transport: received unexpected content-type \"text/html\""}
The agent will reconnect itself, but we can reduce the occurrence of this reconnection (whose main benefit is to do nothing until the server wakes us up), by adding this line to our configuration `nginx` :
The agent will reconnect itself, but we can reduce the occurrence of this reconnection (whose main benefit is to do nothing until the server wakes us up), by adding this line to our configuration `nginx`:
```
location /proto.Woodpecker/Next {