heroku-buildpack-rust VS cargo-make

rocket: 0.5.0-rc.2 diesel: 1.4.4 nightly: in the latest version Heroku Buildpack: https://github.com/emk/heroku-buildpack-rust Also I am using a rust-toolchain file.

I am using this buildpack: https://github.com/emk/heroku-buildpack-rust

You just need to add a Procfile and a buildpack. Just follow the instructions there.

All you have to do is run a binary, so it's pretty easy. And if the service lets you install rustup you can just cargo run as you normally would. For a real example, check out the Heroku buildpack for Rocket.

Use Heroku's Rust buildpack.

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