1 unstable release

0.1.0 Dec 2, 2021

#23 in #block-on

Download history 811/week @ 2024-12-15 544/week @ 2024-12-22 287/week @ 2024-12-29 569/week @ 2025-01-05 596/week @ 2025-01-12 517/week @ 2025-01-19 633/week @ 2025-01-26 707/week @ 2025-02-02 764/week @ 2025-02-09 545/week @ 2025-02-16 671/week @ 2025-02-23 866/week @ 2025-03-02 834/week @ 2025-03-09 1162/week @ 2025-03-16 1763/week @ 2025-03-23 864/week @ 2025-03-30

4,651 downloads per month
Used in tokio_env

Apache-2.0

3KB

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

~1.5MB
~38K SLoC