# pango

[![Crates.io][crates-badge]][crates-url]
[![Docs.rs][docs-badge]][docs-url]
[![MIT licensed][mit-badge]][mit-url]
[![Build Status][actions-badge]][actions-url]

[crates-badge]: https://img.shields.io/crates/v/pango.svg
[crates-url]: https://crates.io/crates/pango
[docs-badge]: https://img.shields.io/docsrs/pango/latest
[docs-url]: https://docs.rs/pango/latest/pango/index.html
[mit-badge]: https://img.shields.io/badge/license-MIT-blue.svg
[mit-url]: https://github.com/plabayo/llama/blob/master/LICENSE
[actions-badge]: https://github.com/plabayo/llama/workflows/CI/badge.svg
[actions-url]: https://github.com/plabayo/llama/actions?query=workflow%3ACI+branch%main

pango is a cross platform TLS Reverse Proxy, written purely in Rust, built on top of [rama](../rama).
It can be used either as a standalone binary where it is used as part of your backend infrastructure,
or as a library in order to use pango as a [Tower][tower] service which wraps your _Http_ service.

> pango is in early development and not ready for production use yet.
> Use this framework at your own risk and your own responsibility.

[Axum](https://github.com/tokio-rs/axum) is the recommended http server library of choice
should you wanna go for the latter approach, as it will fit nicely with the rest of the code.

Here is a high level overview of how pango's services are composed:

```
tcp::Server
 ⤷ tcp::middleware::*
     ⤷ tls::Server
         ⤷ tls::middleware::*
             ⤷ tcp::Client ⭢ /target/
```