mirror of
https://github.com/bigchaindb/bigchaindb.git
synced 2024-10-13 13:34:05 +00:00
dbabe94887
Solution Since BigchainDB and Tendermint are so tightly coupled we need to introduce a process supervisor to make them act like a single microservice, so that if BigchainDB crashes, Tendermint does as well and both are restarted and Tendermint requests a connection towards the proxy app. In Kubernetes, they can be exposed as part of a one POD. For BigchainDB as a system service/process, we need to introduce a process supervisor such as systemd. This PR only solves the former. Changes Upgrade deployment from Tendermint v0.12.0 to v0.19.0 Update some documentation Fix nginx-http entrypoint issues. Update generate-configs.sh script to handle config generation without https-certificates. Update Dockerfile to process dependency links introduced by abci Integrate BigchainDB and Tendermint as a single microservice. This required making BigchainDB to be exposed as a statefulset. Introduce new liveness probe checks. Issues Resolved Partially fixes #2232
11 lines
255 B
Plaintext
11 lines
255 B
Plaintext
# Serve the public key for a tendermint instance
|
|
|
|
server {
|
|
listen PUBLIC_KEY_ACCESS_PORT default_server;
|
|
listen [::]:PUBLIC_KEY_ACCESS_PORT default_server ipv6only=on;
|
|
location / {
|
|
root /usr/share/nginx/;
|
|
autoindex on;
|
|
}
|
|
}
|