[READ ONLY MIRROR] Envoy REST/proto API definitions and documentation. (grpc依赖)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
Taiki Ono ae65079d75 stats: add config and docs for dog statsd sink (#325) 7 years ago
..
root stats: add config and docs for dog statsd sink (#325) 7 years ago
README.md docs: migrate main Envoy repo docs to data-plane-api. (#232) 7 years ago
build.sh stats: add config and docs for dog statsd sink (#325) 7 years ago
conf.py docs: versioning fixes (#233) 7 years ago
publish.sh docs: change publish path (#235) 7 years ago
requirements.txt docs: sphinx and initial protodoc support for RST generation. (#212) 7 years ago

README.md

Developer-local docs build

./docs/build.sh

The output can be found in generated/docs.

How the Envoy website and docs are updated

The Envoy website, and docs are automatically built, and pushed on every commit to master. This process is handled by Travis CI with the publish.sh script.

In order to have this automatic process there is an encrypted ssh key at the root of the envoy repo (.publishdocskey.enc). This key was encrypted with Travis CLI and can only be decrypted by commits initiated in the Envoy repo, not PRs that are submitted from forks. This is the case because only PRs initiated in the Envoy repo have access to the secure environment variables (encrypted_b1a4cc52fa4a_iv, encrypted_b1a4cc52fa4a_key) used to decrypt the key.

The key only has write access to the Envoy repo. If the key, or the variables used to decrypt it are ever compromised, delete the key immediately from the Envoy repo in Settings > Deploy keys.