中文版 README

This is the project we used to build enterprise-oriented generic proxy solutions, including but not limited to proxy / reverse proxy / load balancer / nat traversal.

G3 Project is make up of many components.

The project level docs resides in the doc subdirectory, and you should see the links below for the important ones. Each component will have its own doc in its doc subdirectory.

A generic forward proxy solution, but you can also use it as tcp streaming / transparent proxy / reverse proxy as we have basic support built in.

See g3proxy for detailed introduction.

A work in progress reverse proxy solution.

A benchmark tool, which support HTTP 1.x / HTTP 2 / TLS Handshake / Cloudflare Keyless.

A tool to make root CA / intermediate CA / TLS server / TLS client certificates.

Fake certificate generator for g3proxy.

Only Linux is supported currently. But we are open to PRs to add support to other platforms.

Follow dev-setup.

Follow standards.

We will set tags for each release of each component, in the form <name>-v<version>. You can use these tags to generate source tarballs. And we have added deb and rpm package files for each component that is ready for distribution.

If you want to do a release build:

1. generate a release tarball

   ./scripts/release/build_tarball.sh <name>-v<version>

   All vendor sources will be added to the source tarball, so you can save the source tarball and build it offline at anywhere that have the compiler and dependencies installed.

2. build the package

   For deb package:

   tar xf <name>-<version>.tar.xz
   cd <name>-<version>
   ./build_deb_from_tar.sh

   For rpm package:

   tar xvf <name>-<version>.tar.xz ./<name>-<version>/<name>.spec
   cp <name>-<version>.tar.xz ~/rpmbuild/SOURCES/
   rpmbuild -ba ./<name>-<version>/<name>.spec

If you want to build a package directly from the git repo:

• For deb package:

  ./build_deb_from_git.sh <name>

• For rpm package:

  ./build_rpm_from_git.sh <name>

Please check Contributing for more details.

Please check Code of Conduct for more details.

If you discover a potential security issue in this project, or think you may have discovered a security issue, we ask that you notify Bytedance Security via our security center or vulnerability reporting email.

Please do not create a public GitHub issue.

This project is licensed under the Apache-2.0 License.