Anders Pitman b795ee0bc9 Remove unused custom SSH key code
Was originally planning to allow people to upload public keys to
use for tunnels, but so far no one has asked for this and I
haven't needed it.
2021-12-21 13:14:01 -07:00
2021-01-23 11:16:50 -07:00
2021-02-07 07:57:03 -05:00
2021-12-14 15:04:34 -07:00
2021-12-14 14:58:38 -07:00
2021-12-21 13:14:01 -07:00
2020-12-07 21:41:45 -07:00
2021-12-21 13:14:01 -07:00
2021-12-14 15:04:34 -07:00
2021-12-20 00:46:26 -07:00
2021-12-20 00:46:26 -07:00
2021-12-19 19:38:17 -07:00
2020-11-04 07:55:43 -07:00
2020-10-21 09:50:12 -06:00
2020-10-22 10:08:20 -06:00
2020-10-26 11:11:14 -06:00
2021-12-14 15:04:34 -07:00
2021-12-14 15:43:06 -07:00
2020-11-24 19:21:59 -07:00
2021-02-22 23:04:43 -07:00

Disclaimer

boringproxy is currently beta-quality software. While I am a big believer in open source, my primary goal at the moment is to build a sustainable business around the code I write. So for the most part I can only afford to spend time fixing problems that arise in my own usage of boringproxy. That said, feel free to create GitHub issues and I'll try to help as I have time.

What is it?

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.

Building

git clone https://github.com/boringproxy/boringproxy
cd boringproxy

If you don't already have golang installed:

./install_go.sh
source $HOME/.bashrc
go build

Running

Server

boringproxy server -admin-domain bpdemo.brng.pro

Client

boringproxy client -server bpdemo.brng.pro -token fKFIjefKDFLEFijKDFJKELJF -client-name demo-client -user demo-user
Description
Simple tunneling reverse proxy with a fast web UI and auto HTTPS. Designed for self-hosters.
Readme 640 KiB
Languages
Go 88.2%
Shell 10.6%
Dockerfile 1.2%