#tokio #async #run-time #variables #thread-pool #environmental #worker-thread

tokio_env

An utility library to configure the tokio runtime via environmental variables

3 unstable releases

0.1.0 Dec 2, 2021
0.0.2 Oct 4, 2021
0.0.1 Oct 4, 2021

#523 in Configuration

Download history 1828/week @ 2024-07-27 1527/week @ 2024-08-03 1364/week @ 2024-08-10 1231/week @ 2024-08-17 725/week @ 2024-08-24 804/week @ 2024-08-31 536/week @ 2024-09-07 709/week @ 2024-09-14 1057/week @ 2024-09-21 752/week @ 2024-09-28 765/week @ 2024-10-05 668/week @ 2024-10-12 1138/week @ 2024-10-19 3789/week @ 2024-10-26 1536/week @ 2024-11-02 1495/week @ 2024-11-09

8,120 downloads per month

Apache-2.0

7KB

tokio-env

A configuration library for convenient setup of the tokio runtime.

Configuration

All configuration is made vie environmental variables. The following variables are supported:

  • TOKIO_ENABLE_ALL Whether to enable all types of thread pools. Defaults to true.
  • TOKIO_BLOCKING_THREADS The amount of blocking threads to use.
  • TOKIO_WORKER_THREADS The amount of worker threads to use.
  • TOKIO_THREAD_STACK_SIZE The size of the stack for the created threads.
  • TOKIO_THREAD_NAME The name for the created thread pool(s).

If the environment variable is not provided, it will fall back to the tokio defaults, except for the TOKIO_ENABLE_ALL which defaults to true.

So an empty configuration unfolds like this:

tokio::runtime::Builder::new_multi_thread()
    .enable_all()
    .map(|runtime| runtime.block_on(fun));

Usage

Usage of this library could look like this:

fn main() {
    println!("Initializing tokio runtime...");
    let exit_code = tokio_env::start_with(run)
        .expect("Failed to start tokio runtime!");
    println!("Tokio runtime exited with code: {}", exit_code)
}

async fn run() -> i32 {
    println!("Program started!");
    // Your async logic here
    0
}

But... why?

I'm tired of writing the same boilerplate code over and over again, so I made it a one-liner!

Dependencies

~3.5–9MB
~84K SLoC