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.

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

Jump to bottom

docs: add section for running Envoy via CLI #21811

Merged
merged 5 commits into from
Jul 1, 2022
Merged

docs: add section for running Envoy via CLI #21811

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
96572db
docs: add example for running Envoy via CLI
martinezlucas98 Jun 21, 2022
3e29f97
Apply suggestions from code review
martinezlucas98 Jun 22, 2022
0093ede
docs: Update "Running the built Envoy binary on the host system" cons…
martinezlucas98 Jul 1, 2022
8c8182c
docs: Update "Running the built Envoy binary on the host system"
martinezlucas98 Jul 1, 2022
14b37b9
Move "Running the built Envoy binary..." section above "Testing Envoy…
martinezlucas98 Jul 1, 2022
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
6 changes: 4 additions & 2 deletions bazel/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -272,12 +272,14 @@ for how to update or override dependencies.

## Running the built Envoy binary on the host system

After Envoy is built, it can be executed via CLI.
After Envoy is built, it can be executed via CLI.

As Bazel's current ability to provide information about where it just built the artifacts is limited (as stated in [bazel's issue #8739](https://github.com/bazelbuild/bazel/issues/8739)), we can use the `bazel info bazel-genfiles` command to get the path where Envoy was built.
phlax marked this conversation as resolved.
Show resolved Hide resolved

For example, if Envoy was built using the `bazel build -c opt //source/exe:envoy-static` command, then it can be executed from the project's root directory by running:
phlax marked this conversation as resolved.
Show resolved Hide resolved

```console
bazel-bin/source/exe/envoy-static --config-path /path/to/your/envoy/config.yaml
$(bazel info bazel-genfiles)/source/exe/envoy-static --config-path /path/to/your/envoy/config.yaml
```

## Building Envoy with the CI Docker image
Expand Down