Yonas Yanfa

Thanks, I'm getting another error now: ```sh error[E0425]: cannot find value `MAP_ANONYMOUS` in this scope --> core/storage/buffer_pool.rs:444:27 | 444 | MAP_PRIVATE | MAP_ANONYMOUS, | ^^^^^^^^^^^^^ not found in this scope...

Thanks @pedrocarlo, that worked. It's now failing at sqlite3: ```sh error: failed to run custom build command for `libsqlite3-sys v0.35.0` Caused by: process didn't exit successfully: `/memfs/t/target/release/build/libsqlite3-sys-194280417b0f87fb/build-script-build` (exit status: 1)...

I'm running `cargo build --release` in the root directory.

I think it's running out of memory and giving a `SIGKILL`: ```sh $ cargo build -p turso_core -p turso --release ... error: could not compile `turso_core` (lib); 3 warnings emitted...

@kzantow Thanks!

Actually, using the `.gitignore` file is pretty handy in continuous integration environments. I'll reopen this.

Thanks @martintc, if you could take the lead, that'd be great.

I found a copy in https://github.com/sozu-proxy/sozu/blob/main/doc%2Farchitecture.md

> A client-side certificate is requested during the TLS handshake, though the server does not enforce that the client provides one. Would calling this mTLS be misleading. The presence and...

I still think there should atleast be a flag to enforce client presence and validation.