cargo-make VS config-rs

cargo-make aims to be an extensive Rust-written task runner that additionally lets you define workflows to execute your tasks. You can install it using cargo install cargo-make.

You might be interested in cargo-make, which is based on TOML, or Just, which has a syntax that is vaguely inspired by Make but much less weird sigils and more suited to non-file-based tasks.

I would like to rewrite this project in Rust, but I am not so familiar with Cargo as I am with Make. Is it possible to declare these kinds of rules and targets ? Should I use a build script, a custom tool like cargo-make or something else ? What do you think ?

I use just myself, and I personally don't want projects' codebase to decide when something gets cargo installed on my system. For people who feel that's more acceptable, I'll note that cargo-make has first class support for the idea of expressing a task that depends on a cargo plugin:

Thank you for the help, created ticket #787 and #788!

https://github.com/sagiegurari/cargo-make

I ended up using it over just because it felt easier to use cross platform, and toml seemed like a right choice

cargo make is used pretty extensively in Bottlerocket OS

Cargo is a pretty robust build tool on it's own, but for that extra automated workflow oomph, I also use cargo-make

I like config.rs, but I am struggling to overwrite config profiles with environment variables. The desired config is mixed, like .toml

Consider config crate. It could be like:

I've been using Config most of the time. I also use once_cell to make it a static variable.

I've enjoyed using this one: https://crates.io/crates/config

Anyone know of a library like https://github.com/netflix/go-env but for rust? I found https://github.com/mehcode/config-rs but it's just not as simple...

I was just in that space today. The config crate has an example you might find useful: https://github.com/mehcode/config-rs/tree/master/examples/hierarchical-env

How it differs from config?

Checking an environment variable is very easy with std::env::var or similar. If you have other bits of configuration that also change—which is typical; things like DB connection strings—you may consider a more full-featured solution like https://docs.rs/config/0.10.1/config/ (pay particular attention to this example, which seems to be very close to what you want: https://github.com/mehcode/config-rs/blob/master/examples/hierarchical-env/src/settings.rs ).

It's unfortunate, it looks like there was an attempt to get someone else to maintain it here, but no one ended up really stepping up to the plate.