#tokio #async #variables #fun #block-on #tokio-env

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

#871 in Configuration

Download history 696/week @ 2024-12-17 561/week @ 2024-12-24 329/week @ 2024-12-31 596/week @ 2025-01-07 609/week @ 2025-01-14 644/week @ 2025-01-21 620/week @ 2025-01-28 704/week @ 2025-02-04 826/week @ 2025-02-11 524/week @ 2025-02-18 846/week @ 2025-02-25 867/week @ 2025-03-04 973/week @ 2025-03-11 1316/week @ 2025-03-18 1651/week @ 2025-03-25 1028/week @ 2025-04-01

5,118 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–10MB
~85K SLoC