mirror of https://github.com/boringproxy/boringproxy.git synced 2025-02-25 18:55:29 -06:00

Simple tunneling reverse proxy with a fast web UI and auto HTTPS. Designed for self-hosters.

Go to file

Anders Pitman cfcd781276 Filter UI requests through API API is now the central control point for making authorized requests. The current architecture is: * db simply returns all data * api uses tokens to filter data from db. It includes methods for returning objects, and HTTP endpoints for return JSON. * ui calls the api functions to get filtered data.		2020-10-14 09:17:04 -06:00
webui	Forgot to add some of the templates	2020-10-13 11:29:56 -06:00
api.go	Filter UI requests through API	2020-10-14 09:17:04 -06:00
auth.go	Automatically create admin user on first start	2020-10-13 09:48:03 -06:00
boringproxy.go	Filter UI requests through API	2020-10-14 09:17:04 -06:00
client.go	Move web ui into separate struct and rename file	2020-10-11 13:45:46 -06:00
database.go	Do more authorization checking	2020-10-13 11:21:42 -06:00
go.mod	Start implementing custom client	2020-09-30 23:49:03 -06:00
go.sum	Start implementing custom client	2020-09-30 23:49:03 -06:00
main.go	Start implementing remote-controlled clients	2020-10-09 10:05:31 -06:00
README.md	Remove SirTunnel stuff from readme	2020-09-29 15:53:10 -06:00
todo.md	Filter UI requests through API	2020-10-14 09:17:04 -06:00
tunnel_manager.go	Do more authorization checking	2020-10-13 11:21:42 -06:00
tunnel.sh	Clean up unused attributes	2020-10-12 18:22:08 -06:00
ui_handler.go	Filter UI requests through API	2020-10-14 09:17:04 -06:00
utils.go	Automatically create admin user on first start	2020-10-13 09:48:03 -06:00

README.md

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.