boringproxy development is sponsored by TakingNames.io. boringproxy offers full integration with TakingNames.io, providing the simplest way to get up and running with your own domain. More information here, and a demo video of boringproxy working with TakingNames.io here.
If you run into problems running boringproxy, the best place to ask for help is over at the IndieBits community, where we have a dedicated section for boringproxy support. If you think you've found a bug, or want to discuss development, please open an issue.
If you have a webserver running on one computer (say your development laptop), and you want to expose it securely (ie HTTPS) via a public URL, boringproxy allows you to easily do that.
NOTE: For information on downloading and running boringproxy, it's best to start on the website, boringproxy.io. The information in this README is just for building from source.
git clone https://github.com/boringproxy/boringproxycd boringproxyIf you don't already have golang installed:
./install_go.sh
source $HOME/.bashrcMake the logo image file. It gets baked into the executable so it needs to be available at build time. Note that you don't have to use the official logo for the build. Any PNG will do. It's currently just used for the favicon.
./scripts/generate_logo.shcd cmd/boringproxy
go buildTo build with version information:
go build -ldflags "-X main.Version=$(git describe --tags)"Give the executable permission to bind low ports (ie 80/443):
sudo setcap cap_net_bind_service=+ep boringproxy./boringproxy server./boringproxy client -server bpdemo.brng.pro -token fKFIjefKDFLEFijKDFJKELJF -client-name demo-client -user demo-user