ci Documentation

1. Project Overview & Quickstart (envoyproxy/ci) Copy Chapter

ci

Open-source repository envoyproxy/ci

Repository Details Copy Section

• Repository: envoyproxy/ci
• Primary Language: Code

Note: High-volume repository documentation is actively indexed and synchronized by YakaAI.

2. Official Technical Reference & Guides (envoyproxy/envoyproxy.github.io) Copy Chapter

Envoy website

This is the repo for the Envoy website.

The website is built with bazel using Pelican and Sphinx.

The site is deployed to Netlify.

Envoy's documentation for release versions is stored in https://github.com/envoyproxy/archive/.

Contribute content to the website Copy Chapter

Site data Copy Section

Site data is stored (or created) in yaml files in the site/data directory.

Add adopter logo Copy Section

Envoy is happy to recognize projects that use the software in production.

These are not intended to be an advertisement, but a show of support for the project.

All supporting organizations will be listed in alphabetical order.

To be added to our adopter list, you must meet at least 2 of these criteria:

• Be a participant and active contributor in the community, eg:
  • contributing code
  • raising or resolving issues
  • sponsoring EnvoyCon
• Publicly disclose your usage of Envoy, eg:
  • talk
  • blog
  • CNCF case study
  • social media
• Have an existing Envoy maintainer vouch for and approve your pull request

To add your logo, please send a pull request.

Envoy website development Copy Chapter

Sphinx is used to build the latest docs, and Pelican is used to assemble the static files into a site.

The build process is managed by bazel to ensure reproducible builds and manage external data.

All content, data and customizations are stored in the site directory

Build using Docker Copy Section

This is the recommended way to build the site.

The composition is designed to make use of a Bazel cache on your host system.

Docker: export your `UID`

By default Docker cannot see your user's UID, so you need to export it to run the container build.

This ensures that any files created inside the container - the site build and any cache files - are owned
by the host user.

$ export UID

Docker: build the website

$ docker compose up --build -d website

This will take some time on first run - you can tail the logs with:

$ docker compose logs -f

Once the build has completed the website should be available at http://localhost:8000.

If you are not running the automatic rebuild and you make changes you can rebuild the site with:

$ docker compose run build

Build the site on your host machine Copy Section

If you would prefer not to use Docker you can build directly on your host machine.

Host: install bazel

The expected version of Bazel can be seen in .bazelversion.

It is recommended to install Bazel with Bazelisk as this will pull in the
correct Bazel version.

If you have Yarn installed you can install Bazelisk with that.

From inside your local copy of the envoy-website repository, run:

$ yarn

Host: install a compiler

You will need a compiler (clang or GCC) and some related dev tools installed to build the docs.

For example, on a Debian-based system, these can be installed with:

$ apt get install build-essential

If you build without the docs, you can ignore this requirement.

Host: build the website

$ ./build-website.sh

Tips for site development Copy Section

Automatically rebuild during development

The site can be made to auto-rebuild when changes occur in the site/ directory.

If you are using Docker you can trigger this by setting the following in your environment,
before bringing up the Docker composition:

$ export BUILDER=live
$ docker compose up --build -d website

If you are building on your host you can just run the rebuild script directly:

$ ./rebuild.sh ./site ./build-website.sh

Build without the docs

If you only need the non-docs parts of the website to be built, set the following environment
variable.

Set this before building in Docker or on your host:

$ export BAZEL_BUILD_OPTIONS="--config=nodocs"

Debug build

You can enable richer logging.

Set the following environment variable before building in Docker or on your host:

$ export DEBUG=1

Put frequently used env vars in `.env`

Docker compose will source the .env file before running.

For example, if you always want the site to build "live", add the following to .env

export BUILDER=live