rustshop VS nocargo

I was hoping to have https://github.com/rustshop/rustshop be like that, but I've got a Rust dayjob since then, and I have less time for Rust side projects now.

Many thanks to u/dpc_pw, whose notes on GitHub were my starting point for the flake definition. (I also just realized I unwittingly gave my article an almost-identical title by the time I was done refining it, so I’m more indebted to them than I thought.)

Since docker images are mentioned, I'd like to point out that using musl-linked images is often counterproductive, as docker layers with standard library can be shared between different projects and build versions. https://github.com/rustshop/rustshop/discussions/9

and here is the project in this area that I'm working on

rustshop is an attempt at building a template for developers to help them start their own cloud-based system, without much Ops experience.

If you want to iterate with nix instead of cargo, crate2nix and cargo2nix provides more caching and more fine control over your dependencies. I haven't used these two so you would have to decide for yourself. You may also want to try out nocargo for something more experimental.

Thank you. It looks very useful, so I’ll give it a try. Do you know, offhand, whether I can use crane to build a dependency specified in Cargo.toml with extra settings? I have a more complicated Rust application I’m trying to build with Nix. The solution I’ve arrived at for the moment is building with nocargo just so I can override OUT_DIR when building opencv, but it doesn’t work with LTO and the end result is inferior to my starting point. (If there’s a way to customize the opencv build without needing any extra packages, I’d love to hear about that too.)