#tokio #async #run-time #variables #env-var #thread-pool #environmental

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

#626 in Configuration

Download history 1031/week @ 2024-05-03 1247/week @ 2024-05-10 797/week @ 2024-05-17 532/week @ 2024-05-24 868/week @ 2024-05-31 593/week @ 2024-06-07 1210/week @ 2024-06-14 638/week @ 2024-06-21 887/week @ 2024-06-28 762/week @ 2024-07-05 792/week @ 2024-07-12 918/week @ 2024-07-19 1355/week @ 2024-07-26 1717/week @ 2024-08-02 1442/week @ 2024-08-09 952/week @ 2024-08-16

5,572 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–4.5MB
~82K SLoC