cross VS nexus-repository-cargo

The -musl targets for Linux make it easy to dodge the need to compile against the oldest glibc you want to support if your project is pure Rust and cross is a Docker wrapper which aims to make cross-targeting in other scenarios as easy as with Go.)

...though, funny enough, if you have enough experience with Rust to not get bogged down in the details and you use cross to work around Rust's "take your time but get it right" approach to cross-building, Rust is often better at little CLI tools, purely because of how valuable it is to be able to teach the type system to check so many invariants at compile time.

Another thing to keep in mind for if just using the musl target with your usual setup is insufficient (eg. if you need to use a crate like ttspico which statically links some C code) is cross, which makes it really easy to use Docker to build and run tests.

I'm primarily a Go developer, and for that we use Sonatype Nexus to cache dependencies online, and we sync those offline to pull from. That works pretty well for us, and we use this for a bunch of languages like Ruby, C#, NodeJS, etc. But it looks like Nexus doesn't support Cargo, and the only community plugin I could find only supports hosting, while I need a proxy. I did see Artifcatory has some level of Cargo support, but we have to have an open-source solution. We also mirror the Ubuntu repositories, so we get our C/C++ libraries through that. I've noticed Rust dependencies in there, but they don't work through Cargo from what I've seen.