cargo

In the docs, there are several cases such as here where code snippet examples are shown side by side, without actually specifying which files they are (eg. deny.toml vs Cargo.toml) which can lead to confusion for users. Every code snippet should just specify # <name>.toml at the top for clarity.

Link to minimal repo: https://github.com/prestontw/cargo-chef-vendored-repo

I've vendored the dependencies of a small Rocket app using cargo vendor. I've then updated .cargo/config.toml so that cargo build uses the local dependencies. Trying to run cargo chef errors with checksum changes (since cargo chef has replaced all of the lib.rs files in the dependencies with empty files?).

This is a tracking issue for additional Store implementations.

Here is a non-exhaustive list of potential candidates for an Store implementation:

• S3Storage:
  This would store crate tarballs and rendered README pages into Amazon's S3.
• RemoteStorage:
  Requires to implement a companion server.
  The idea is to have a reserved folder on another machine which runs a comp

• Derive serialization for the configuration keys.
• Add the serialized configuration to the fingerprint hash.