postrust-engine 2.3.1

The REST request pipeline of Postrust, from HTTP request to response, independent of any web framework
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22

# postrust-engine

The REST request pipeline of [Postrust](https://postrust.org/), independent of any web framework: an `http::Request` in, the `http::Response<Bytes>` the PostgREST-dialect API answers with out.

Authentication, request parsing, planning, execution against PostgreSQL inside a transaction that sets the token's role and claims, embedding, counting and media handlers all live here. [`postrust-server`](https://crates.io/crates/postrust-server) wraps it in axum. A host that cannot run axum, such as a Cloudflare Worker, calls it directly ([issue #50](https://github.com/postrust/postrust/issues/50)).

Most users want the `postrust` binary from `postrust-server`, not this crate.

## Part of Postrust

| Crate | Role | Docs |
|-------|------|------|
| [`postrust-server`](https://crates.io/crates/postrust-server) | HTTP server | [docs.rs](https://docs.rs/postrust-server) |
| **`postrust-engine`** (this crate) | REST request pipeline | [docs.rs](https://docs.rs/postrust-engine) |
| [`postrust-core`](https://crates.io/crates/postrust-core) | Parsing, planning, schema cache | [docs.rs](https://docs.rs/postrust-core) |
| [`postrust-sql`](https://crates.io/crates/postrust-sql) | SQL builder | [docs.rs](https://docs.rs/postrust-sql) |
| [`postrust-auth`](https://crates.io/crates/postrust-auth) | JWT authentication | [docs.rs](https://docs.rs/postrust-auth) |
| [`postrust-response`](https://crates.io/crates/postrust-response) | Response formatting | [docs.rs](https://docs.rs/postrust-response) |

## License

MIT